An event companion and onboarding experience for the ATmosphere (alpha)
atmo.quest
Update readme
authored by
Brittany Ellich
and committed by
Tangled
(Jun 1, 2026, 3:21 PM UTC)
a53aa4e4
3201de6a
+5
-9
+5
-9
deploy/tap/README.md
+5
-9
deploy/tap/README.md
···
26
26
27
27
## Deploying
28
28
29
-
Redeploys go through one **manual** Tangled pipeline:
30
-
[deploy-tap.yml](../../.tangled/workflows/deploy-tap.yml). Trigger it from the
31
-
repo's Pipelines page (any branch — `manual` ignores the branch filter). It
32
-
just runs `flyctl deploy` from this directory, so it needs `FLY_API_TOKEN` in
33
-
the repo's Tangled settings → secrets.
29
+
Redeploys run on merge/push to `main` via
30
+
[deploy-tap.yml](../../.tangled/workflows/deploy-tap.yml), alongside the main
31
+
`atmoquest` deploy. It just runs `flyctl deploy` from this directory, so it
32
+
needs `FLY_API_TOKEN` in the repo's Tangled settings → secrets. A version bump
33
+
takes effect by editing `INDIGO_VERSION` in the Dockerfile and merging to main.
34
34
35
35
Equivalently, by hand: `( cd deploy/tap && flyctl deploy --remote-only )`.
36
-
37
-
Tap rarely changes, so it is intentionally **not** part of the per-push
38
-
`atmoquest` deploy — redeploy via the pipeline when you bump the indigo/Tap
39
-
version in the Dockerfile.
40
36
41
37
## Keeping versions in sync
42
38