-
Notifications
You must be signed in to change notification settings - Fork 151
docs(cloud): add INIT_CONFIG environment variable documentation for self-hosted deployments #879
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.
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
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for bejewelled-pegasus-b0ce81 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot wasn't able to review any files in this pull request.
…ployment guide Co-authored-by: pontusringblom <170570911+pontusringblom@users.noreply.github.com>
Co-authored-by: pontusringblom <170570911+pontusringblom@users.noreply.github.com>
|
@aabidsofi19, should serverbaseURL come under this section? |
| @@ -1,5 +1,32 @@ | |||
| --- | |||
| title: Planning Layer5 Cloud Deployment | |||
| title: Planning | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot don't change the title.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in commit 8f443c7. The title is now preserved as "Planning" and the frontmatter structure is correct.
|
|
||
| ## Provider Configuration Planning | ||
|
|
||
| When planning your self-hosted Layer5 Cloud deployment, consider how you will initialize and configure your provider instance. The `INIT_CONFIG` environment variable enables you to automate provider configuration during deployment. | ||
|
|
||
| ### Configuration Strategy | ||
|
|
||
| Before deploying, plan your configuration approach: | ||
|
|
||
| 1. **Provider Identity**: Define your provider name and identification | ||
| 2. **Initial Settings**: Determine which settings need to be configured at startup | ||
| 3. **Configuration Management**: Decide how configuration will be managed (environment variables, secrets, config files) | ||
| 4. **Update Strategy**: Plan for configuration updates and changes over time | ||
|
|
||
| ### Using INIT_CONFIG for Automated Setup | ||
|
|
||
| The `INIT_CONFIG` environment variable allows you to pre-configure your provider during deployment, eliminating manual setup steps. This is particularly valuable for: | ||
|
|
||
| - **Reproducible Deployments**: Ensure consistent configuration across environments | ||
| - **CI/CD Integration**: Automate deployments with predefined configurations | ||
| - **Infrastructure as Code**: Manage provider configuration alongside your infrastructure | ||
|
|
||
| For detailed usage and examples, see the [Deployment Guide](/cloud/self-hosted/deployment/#init_config). | ||
|
|
||
| {{< alert type="warning" title="Important" >}} | ||
| Plan your INIT_CONFIG carefully as it is only processed during initial startup. Changes require redeployment or manual configuration updates. | ||
| {{< /alert >}} Layer5 Cloud Deployment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should not be included in the frontmatter, but should be in the body, @copilot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in commit 8f443c7. The Provider Configuration Planning section is now properly placed in the body after the frontmatter closes with ---.
Co-authored-by: pontusringblom <170570911+pontusringblom@users.noreply.github.com>
Documentation Update for INIT_CONFIG Environment Variable
/content/en/cloud/self-hosted/deployment/Changes Made
1. Deployment Guide (
/content/en/cloud/self-hosted/deployment/_index.md)Added comprehensive Environment Variables section with INIT_CONFIG documentation:
-eflag2. Planning Guide (
/content/en/cloud/self-hosted/planning/_index.md)Added Provider Configuration Planning section:
Documentation Principles Applied
References
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.