Rate this page:
This page describes how to take your existing Forge app from the development environment and share it with your users in a production environment. You'll learn about Forge environment restrictions and how to request the minimum set of permissions from your users.
When you call , we automatically create three environments for you:
Environments are where you deploy your app. Once an app is running in an environment, you can install it from that environment on to an Atlassian site with .
We recommend using the development environment for testing your changes, staging for a stable version of your app, and production as the version of your app that’s ready for use.
By default, the CLI will run commands for the development environment unless you specify another with the flag.
When using the staging environment, you can't use the command. You'll need to redeploy your app using each time you make a code change.
In the production environment, you can't use the or commands.
To debug issues in a production environment, you’ll need to redeploy your affected code to the staging or development environments where you have access to debugging tools. See the Debugging page for more detail.
Forge apps in staging and production must explicitly declare which scopes they require in the to use the authenticated Product Fetch APIs.
See the Permissions page for a summarized table of Forge supported OAuth 2.0 scopes for all Atlassian cloud products. You can also find supported scopes in each product's REST API documentation on a per operation basis.
See the Add scopes to call an Atlassian REST API page for step-by-step instructions on adding new scopes.
To deploy to a specific environment, provide the argument to the Forge CLI commands.
Navigate to the app's top-level directory and deploy your app by running:
forge deploy -e production
Install your app by running:
forge install -e production
Rate this page: