You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-11Lines changed: 25 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,5 @@
1
1
# Forge Hello World
2
2
3
-
This project contains a Forge app written in Javascript that displays `Hello World!` in a Jira issue panel.
4
-
5
3
See [developer.atlassian.com/platform/forge/](https://developer.atlassian.com/platform/forge) for documentation and tutorials explaining Forge.
6
4
7
5
## Requirements
@@ -14,30 +12,46 @@ See [Set up Forge](https://developer.atlassian.com/platform/forge/set-up-forge/)
14
12
15
13
- Modify your app backend by editing the `src/resolvers/index.js` file to define resolver functions. See [Forge resolvers](https://developer.atlassian.com/platform/forge/runtime-reference/custom-ui-resolver/) for documentation on resolver functions.
16
14
17
-
- Build and deploy your app by running:
15
+
In summary, you can run this command to deploy and install the app in the first terminal:
18
16
19
17
```shell
20
18
forge lint --fix
21
19
forge deploy
20
+
forge install -e development -s gitauto.atlassian.net --upgrade --confirm-scopes --non-interactive
21
+
forge tunnel
22
22
```
23
23
24
-
- Install your app in an Atlassian site by running:
24
+
And run this command in the second terminal to see the logs in forge cloud. See [Forge logs](https://developer.atlassian.com/platform/forge/cli-reference/logs/) for more information.
25
25
26
26
```shell
27
-
forge install --upgrade
27
+
forge logs -e development
28
+
# or
29
+
forge logs -e development --grouped
28
30
```
29
31
30
-
- Develop your app by running `forge tunnel` to proxy invocations locally:
32
+
- Use the `forge deploy` command when you want to persist code changes.
33
+
- Use the `forge install` command when you want to install the app on a new site.
34
+
- Once the app is installed on a site, the site picks up the new app changes you deploy without needing to rerun the install command.
35
+
36
+
## Environment Variables
37
+
38
+
For development, you can do the following:
31
39
32
40
```shell
33
-
forge tunnel
41
+
forge variables list -e development
42
+
forge variables set --encrypt SUPABASE_URL <value>
43
+
forge variables set --encrypt SUPABASE_API_KEY <value>
34
44
```
35
45
36
-
### Notes
46
+
For production, you have to do the following:
37
47
38
-
- Use the `forge deploy` command when you want to persist code changes.
39
-
- Use the `forge install` command when you want to install the app on a new site.
40
-
- Once the app is installed on a site, the site picks up the new app changes you deploy without needing to rerun the install command.
48
+
```shell
49
+
forge variables list -e production
50
+
forge variables set --environment production --encrypt SUPABASE_URL <value>
51
+
forge variables set --environment production --encrypt SUPABASE_API_KEY <value>
52
+
```
53
+
54
+
See [Environment variables](https://developer.atlassian.com/platform/forge/cli-reference/variables/) for more information.
0 commit comments