Due to the flexibility and varied setups of existing Connect apps, we can't recommend a specific dev loop between the Forge and Connect parts of your app.
Whatever your setup, you now have some features available to help optimize your development lifecycle.
can and should be set differently in different environments (development, staging, production), but the field in your manifest (manifest.yml) is not environment-specific. This means needs to be changed to the appropriate key before running into a different environment.
An app with the same can only be installed once on a single site.
The installation of a second app environment with the same app will be blocked.
can be changed in any non-production environment at any time.
In production, your key should always match your existing Connect to ensure upgrades work as expected.
is used by several Atlassian Connect features as an identifier, and these are affected by the change. For example, the app loses access to:
Any app properties it has written, such as the resource.
Certain existing configured modules identified by the key, such as workflow post functions.
Bookmarked URLs that include the app key, such as links to general pages, space tools tabs, or reports.
We understand existing Connect developers may have their own way of automating changes. Due to the flexibility of developer environments with Connect, we don't have a specific recommended approach, though deploy.js has some code to automate this.
Tunneling allows you to run your Forge app code locally on your machine, making Forge development faster.
You could use tunneling with your existing methods of updating your Connect app to quickly test your changes.
Forge allows you to control how different people can work together on your app.
Manage your app contributors
Learn how to create custom environments for different developers
Once you've started using Forge, you can use the developer console to:
Some of these logs will only output data where your app is using Forge modules or functions.
Rate this page: