nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Forge App deployment and testing

Chuck Talk

I have a Forge app, the build works, the console says "eligible for Runs on Atlassian," but I need to know how to deploy to a dev environment. I deployed on a One Atlassian site, and that seems to stay constant. My change in the app interface never refreshes when I do a

forge install -- upgrade

command, so I am not certain if my changes are effective. New to delivering apps, but have lots of ideas to add here. What would you advise so that I can test this out thoroughly before deploying to market?

Accepted answers

Florian Bonniec

Hi @Chuck Talk

I think the question should be raised in the Atlassian developer community instead.

You can install your app using

forge install

then "update" your code running

forge deploy

When you update the manifest you will need to upgrade

forge install --upgrade

You can specify env (dev by default) --environment staging

The command line will ask you to input the site url.

Regards

All comments

Florian Bonniec

Hi @Chuck Talk

I think the question should be raised in the Atlassian developer community instead.

You can install your app using

forge install

then "update" your code running

forge deploy

When you update the manifest you will need to upgrade

forge install --upgrade

You can specify env (dev by default) --environment staging

The command line will ask you to input the site url.

Regards

Chuck Talk

Hi Florian,

Thanks for the answer. I have deployed my app now.

I'm a bit confused why my app icon isn't updating, and why some improvements don't appear, although they exist in code. Maybe it's just a quirk in Forge.

:shrug:

Caterina Curti

Hey @Chuck Talk ,

I would try to use `forge tunnel` (in this way your local version of the app will run and you'll see the logs in the terminal where you are running it) to confirm the changes are actually having the effect you expect.
Once everything works as expected, you can do a `forge deploy`.

Most changes should be visible immediately but, for some of them, there could be a delay up to 10 minutes.

The browser console can help you see which version of the app is currently running.
I usually have a prefix (see the LOG_PREFIX) variable in this repo (https://bitbucket.org/atlassian/forge-presentations/src/main/00.forge-app-jam/Ep4_ShowFlag_PopUp/src/frontend/background-script.jsx) to help me check which version is running. That's very handy as well to filter only the app related logs in the console.

Cheers,
Caterina

Chuck Talk

Hi Caterina!

Long time no Talk.

I figured out my issue and have two MVPs already built out now. It is fun to build things, and I am hopeful that my tools will be useful.

Thanks for that tip as well' that is useful.

Sincerely,

Chuck

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

confluence-cloud

development

forge