FeaturePeek Help
Go to website
Back
Articles on:
Deployments
Options available to set on your deployments.
How to set a deployment's entry path
The entry path is the initial route your deployment's visitors will land on when reviewing your pull request on FeaturePeek. If your front-end changes only affect the appearance of your website's blog, then you can point the entry path to /blog in order to save your reviewers a click or two. This also updates the thumbnail in your team's Dashboard so that you can easily identify it among other open pull requests. The easiest way to set the entry path
Popular
How to set environment variables
If you specified type: docker in your project's peek.yml file, you have the ability to modify runtime environment variables for each of your project's deployments. Depending on your code, some environment variables may be required for your application to boot up and/or behave correctly. On your team's Dashboard, click the Settings icon next to your project's name.  menu. Shutting down the deployment will kick out any reviewer currently looking at it, so be sure that no one on your team is doing anything important in that particular deployment. ![](https://storage.crisp.chat
Some readers
How to set a deployment to be public
Teams on the Business plan have the ability to set their projects and deployment previews to be public. When a deployment is public, anyone with the link to it can view it. Projects, and the deployments within them, are private by default. You can easily tell whether a deployment is public or private by looking at the lock icon on the FeaturePeek drawer of every running deployment. You can also change the public/private setting for the project as a whole in the project settings. Future pull
Some readers