|
| 1 | +--- |
| 2 | +date: 2022-04-12 |
| 3 | +title: "The PipeCD play environment is here!!!" |
| 4 | +linkTitle: "The PipeCD play environment" |
| 5 | +weight: 994 |
| 6 | +description: "In this post, we will have a glance at the play environment of PipeCD, how to access and what you can get from the environment." |
| 7 | +author: Khanh Tran ([@khanhtc1202](https://twitter.com/khanhtc1202)) |
| 8 | +--- |
| 9 | + |
| 10 | +Good news, PipeCD team's happy to bring you a place where you can have a look at the PipeCD platform in use. We call it the `play environment` - [https://play.pipecd.dev](https://play.pipecd.dev). |
| 11 | + |
| 12 | + |
| 13 | +<p style="text-align: center;"> |
| 14 | +PipeCD play environment view |
| 15 | +</p> |
| 16 | + |
| 17 | +With this live demo, you can now have a look at the PipeCD platform in use without self preparing [quickstart](/docs/quickstart/) or such. It’s way easier (and faster) to make a try by clicking around and seeing how you can get when using PipeCD as the CD platform on your own. |
| 18 | + |
| 19 | +### How to access |
| 20 | + |
| 21 | +The PipeCD play environment console is available at [https://play.pipecd.dev](https://play.pipecd.dev). After following the link, you will get the login page as below. |
| 22 | + |
| 23 | + |
| 24 | + |
| 25 | +Type __play__ to the input box as the project name to login and click to `Continue` to go to the account sign in page. Followed by `LOGIN WITH GITHUB`. |
| 26 | + |
| 27 | + |
| 28 | + |
| 29 | +Then, that's it. Feel free to click around and see what PipeCD can bring to you in real-life use. |
| 30 | + |
| 31 | +#### Some pages you may feel interest |
| 32 | + |
| 33 | + |
| 34 | +<p style="text-align: center;"> |
| 35 | +<a href="https://play.pipecd.dev/applications/913a0bde-1f38-41e3-9f56-75910b8988a9?project=play" target="_blank">Application detail page</a> - show the application's state and info |
| 36 | +</p> |
| 37 | + |
| 38 | + |
| 39 | +<p style="text-align: center;"> |
| 40 | +<a href="https://play.pipecd.dev/deployments/89c4a27a-a268-448a-bb94-bc994863b695?project=play" target="_blank">Deployment detail page</a> - show the deployment's stages and its log |
| 41 | +</p> |
| 42 | + |
| 43 | +You can also have a look at [PlanPreview](https://pipecd.dev/docs/user-guide/plan-preview/) feature example, via the play project application configuration repository named [examples](https://github.com/pipe-cd/examples) at [PR #108 comment](https://github.com/pipe-cd/examples/pull/108#issuecomment-1091098475). |
| 44 | + |
| 45 | + |
| 46 | +<p style="text-align: center;"> |
| 47 | +Plan preview - give the early feedback by showing the changes which will be applied on PR merged |
| 48 | +</p> |
| 49 | + |
| 50 | +### Notes for the PipeCD play environment |
| 51 | + |
| 52 | +1. Since the limitation of the resources, you can only log in with the [Viewer role](/docs/operator-manual/control-plane/auth/#role-based-access-control-rbac). This means you can only click around and see PipeCD team prepared examples, __triggering new deployments or creating new resources are disabled__. |
| 53 | +2. Currently, only applications of kinds: `KUBERNETES`, `CLOUDRUN` and `TERRAFORM` are prepared and available to see on the play environment console. We will add example applications of other kinds (`LAMBDA`, `ECS`, etc.) later. |
| 54 | +3. The [application configuration](/docs/user-guide/adding-an-application/) files for those examples on the play environment are published at [pipe-cd/examples](https://github.com/pipe-cd/examples) repository. Those configuration files are __real-life useable__ configurations, but only on our cluster, since the encrypted credentials placed in those files are ours. You can replace those and use on your own. |
| 55 | + |
| 56 | +Happy PipeCD-ing 👋 |
0 commit comments