Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove incorrect mention of Tigris #1860

Merged
merged 2 commits into from
Nov 6, 2024
Merged

Remove incorrect mention of Tigris #1860

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
063ea21
Remove incorrect mention of Tigris
injoongy Oct 30, 2024
26e3c0b
Add explanation for reconfiguring Tigris
injoongy Nov 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/move-app-org.html.markerb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,10 +30,10 @@ The following app resources are transferred to the new org automatically:
- environment variables and secrets
- certificates and domain names
- LiteFS databases (when `$FLY_APP_NAME` is used for your Consul key in `litefs.yml`)
- Tigris object storage

## Resources that you need to manually reconfigure

The following extension services need to be reconfigured for the app after the move:

- **[Upstash for Redis](https://fly.io/docs/upstash/redis/):** Upstash Redis is only available over an organization's private network. After you move the app, you'll need to provision a new database for the new org.
- **[Tigris object storage](https://fly.io/docs/tigris/):** Before moving the app, you'll need to delete the bucket, then recreate it in the new org and set the new secrets. Billing for the new bucket will be tied to the new org.