Skip to content

Advanced Environment Configuration documentation #39

Open
phurpa-tsering wants to merge 1 commit intomainfrom
doc/advanced-env
Open

Advanced Environment Configuration documentation #39
phurpa-tsering wants to merge 1 commit intomainfrom
doc/advanced-env

Conversation

@phurpa-tsering
Copy link
Collaborator

Advanced Environment Configuration documentation

@phurpa-tsering
Copy link
Collaborator Author

hey @lbenedetto , could you please review this PR?

Comment on lines +85 to +89
```yaml
baseUrl: https://api.example.com
timeout: 5000
featureFlags:
newDashboard: true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't the format of the yaml

Copy link
Contributor

@lbenedetto lbenedetto Feb 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

public

thor:
  variables:
    description: "God of Thunder"
  children:
    production:
      variables:
        BASE_URL: "thor.com"
    test:
      children:
        staging:
          variables:
            BASE_URL: "staging.thor.com"
        local:
          variables:
            BASE_URL: "localhost:8080"
odin:
  variables:
    description: "The Allfather"
  children:
    production:
      variables:
        BASE_URL: "odin.com"
    test:
      children:
        staging:
          variables:
            BASE_URL: "staging.odin.com"
        local:
          variables:
            BASE_URL: "localhost:8080"

private

thor:
  children:
    test:
      variables:
        PASSWORD: "hunter2"

And then in the env selection window, these envs would be available:

thor
thor.production
thor.test
thor.test.staging
thor.test.local
thor
odin.production
odin.test
odin.test.staging
odin.test.local

Two entirely separate trees of env hierarchies in one profile.

Image


## Profiles

Profiles let you maintain multiple named environment configurations — for example, `staging`, `production`, or `local-dev` — each with their own public and private files.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not how profiles should be used. staging, production and local should all be in the default profile. You'll have to ask nikdim about what profiles are for because its actually really difficult to envision a use case for them given just how flexible the system is even only using the default profile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants