+PipeCD play environment view +
+ +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. + +### How to access + +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. + + + +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`. + + + +Then, that's it. Feel free to click around and see what PipeCD can bring to you in real-life use. + +#### Some pages you may feel interest + + ++Application detail page - show the application's state and info +
+ + ++Deployment detail page - show the deployment's stages and its log +
+ +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). + + ++Plan preview - give the early feedback by showing the changes which will be applied on PR merged +
+ +### Notes for the PipeCD play environment + +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__. +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. +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. + +Happy PipeCD-ing 👋 diff --git a/docs/static/images/play-environment-application.png b/docs/static/images/play-environment-application.png new file mode 100644 index 0000000000..0784ac45e2 Binary files /dev/null and b/docs/static/images/play-environment-application.png differ diff --git a/docs/static/images/play-environment-deployment.png b/docs/static/images/play-environment-deployment.png new file mode 100644 index 0000000000..bd4025abc8 Binary files /dev/null and b/docs/static/images/play-environment-deployment.png differ diff --git a/docs/static/images/play-environment-github-login.png b/docs/static/images/play-environment-github-login.png new file mode 100644 index 0000000000..3d8e5db914 Binary files /dev/null and b/docs/static/images/play-environment-github-login.png differ diff --git a/docs/static/images/play-environment-login.png b/docs/static/images/play-environment-login.png new file mode 100644 index 0000000000..7eb2200c8a Binary files /dev/null and b/docs/static/images/play-environment-login.png differ diff --git a/docs/static/images/play-environment-overview.png b/docs/static/images/play-environment-overview.png new file mode 100644 index 0000000000..7ed85c3724 Binary files /dev/null and b/docs/static/images/play-environment-overview.png differ diff --git a/docs/static/images/play-plan-preview.png b/docs/static/images/play-plan-preview.png new file mode 100644 index 0000000000..8170c6f9a7 Binary files /dev/null and b/docs/static/images/play-plan-preview.png differ