Updates from experience deploying with FlightControl #11656
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
flybayer
reviewed
Oct 7, 2024
| 3. Click "Create project" (do not add services to the UI during this step, the flightcontrol.json you added will be used for service config) | ||
| 5. After project is created, add your env vars under Environment Settings. | ||
| 1. If using dbAuth, add the session secret key env variable in the Flightcontrol dashboard. | ||
| 2. NOTE: The RedwoodJS Flightcontrol sets up an array of environments and defaults you to the 1st one: 'Development', add to the array to deploy more environments. |
There was a problem hiding this comment.
Suggested change
| 2. NOTE: The RedwoodJS Flightcontrol sets up an array of environments and defaults you to the 1st one: 'Development', add to the array to deploy more environments. | |
| - This will create a `flightcontrol.json` file with an array of environments. It defaults with a single Development environment. Add to the array to deploy more environments. |
| 1. Connect your Github account and select your repo. | ||
| 2. Click "Create Project" and complete any required steps like linking your AWS account. | ||
| 3. Configuration Type should autoselect as `flightcontrol.json`. | ||
| 4. NOTE: `flightcontrol.json` is now the source of truth for your Project and its Environments. |
There was a problem hiding this comment.
Suggested change
| 4. NOTE: `flightcontrol.json` is now the source of truth for your Project and its Environments. | |
| - `flightcontrol.json` is now the source of truth for your Project and its Environments. |
Comment on lines
+20
to
+21
| 6. Add your env vars in Flightcontrol for your Environment. | ||
| 7. If using dbAuth, add the session secret key env variable in the Flightcontrol dashboard. |
There was a problem hiding this comment.
Suggested change
| 6. Add your env vars in Flightcontrol for your Environment. | |
| 7. If using dbAuth, add the session secret key env variable in the Flightcontrol dashboard. | |
| 5. After project is created, add your env vars under Environment Settings. | |
| 1. If using dbAuth, add the session secret key env variable in the Flightcontrol dashboard. |
| 4. NOTE: `flightcontrol.json` is now the source of truth for your Project and its Environments. | ||
| 6. Add your env vars in Flightcontrol for your Environment. | ||
| 7. If using dbAuth, add the session secret key env variable in the Flightcontrol dashboard. | ||
| 8. To tear down your project w/Flight control go to your dashboard and the 'Danger Zone' and choose delete. |
There was a problem hiding this comment.
Suggested change
| 8. To tear down your project w/Flight control go to your dashboard and the 'Danger Zone' and choose delete. | |
| 8. To tear down your project, go to the Flightcontrol dashboard, click on the Project settings icon, and then choose destroy in the 'Danger Zone' tab. |
|
|
||
| If you have _any_ problems or questions, Flightcontrol is very responsive. [See their support options](https://www.flightcontrol.dev/docs/troubleshooting/contacting-support). | ||
| If you have *any* problems or questions, Flightcontrol is very responsive in [their support Discord](https://discord.gg/yY8rSPrD6q). |
There was a problem hiding this comment.
Suggested change
| If you have *any* problems or questions, Flightcontrol is very responsive in [their support Discord](https://discord.gg/yY8rSPrD6q). | |
| If you have _any_ problems or questions, Flightcontrol is very responsive. [See their support options](https://www.flightcontrol.dev/docs/troubleshooting/contacting-support). |
| 2. NOTE: The RedwoodJS Flightcontrol sets up an array of environments and defaults you to the 1st one: 'Development', add to the array to deploy more environments. | ||
| 3. Commit the changes and push to github. | ||
| 4. If you don't have an account, sign up at [app.flightcontrol.dev/signup](https://app.flightcontrol.dev/signup?ref=redwood). | ||
| 5. Create a new project from the onboarding screen or project list. |
There was a problem hiding this comment.
Suggested change
| 5. Create a new project from the onboarding screen or project list. | |
| 5. Create a new project. |
| 4. If you don't have an account, sign up at [app.flightcontrol.dev/signup](https://app.flightcontrol.dev/signup?ref=redwood). | ||
| 5. Create a new project from the onboarding screen or project list. | ||
| 1. Connect your Github account and select your repo. | ||
| 2. Click "Create Project" and complete any required steps like linking your AWS account. |
There was a problem hiding this comment.
Suggested change
| 2. Click "Create Project" and complete any required steps like linking your AWS account. | |
| 2. Click "Create project" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are my updates from using the FlightControl deployment for three months and then tearing it down as too expensive