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 forge create
, 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 forge install
.
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 --environment
flag.
While your app is deployed to development, your app title will have the suffix (DEVELOPMENT)
.
Similarly, while your app is deployed to staging, it will have the suffix (STAGING)
.
Once you deploy your app to production, your app title will no longer have any suffix.
When using the staging environment, you can't use the forge tunnel
command. You'll need
to redeploy your app using forge deploy
each time you make a code change.
When using the production environment, you can't use the forge tunnel
or forge logs
commands.
To debug issues, you’ll need to redeploy your affected
code to the staging or development environments where you have access to
debugging tools.
For apps installed on sites you don’t have access to, you’ll need to ask the app
user to
download the logs for your app and send them to you.
Forge apps must explicitly declare which scopes they require in the manifest.yml
file
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 -e
argument to the Forge CLI commands.
Navigate to the app's top-level directory and deploy your app by running:
1 2forge deploy -e production
Install your app by running:
1 2forge install -e production
Select the product.
Enter the URL for your development site (for example, example.atlassian.net).
Review the scopes your app is requesting then answer y
.
To enable users to use your app, enable sharing through the developer console. For more information, see Distribute your apps.
Rate this page: