Custom zones · 0.8.1

Custom environment and CI configuration

Combine UI profiles with preserved overrides and custom jobs.

On this page

Maintain deployment settings in the UI and add custom overrides where needed. Configuration editing, file generation and server changes are separate actions.

Environment files

Path Owner and purpose
deploy/generated/environments/ENV_NAME.json Generator-owned complete UI profile
deploy/custom/environments/ENV_NAME.json Your partial override
deploy/environments/ENV_NAME.json Optional complete manual profile; takes priority over both files above

ENV_NAME is the profile name, such as production or test, not the project name or placement preset. Save → Generate creates the custom file; {} keeps the UI settings unchanged. Ordinary use does not require copying the generated file into deploy/environments.

Add an override

Put this example in the selected profile's custom file:

{
  "allowedOrigins": [
    "https://admin.example.com",
    "https://app.example.com"
  ]
}

Use your own domains. Arrays replace the complete list, nested objects merge by property, and null removes a property. Do not override schemaVersion, project or environment, add unknown properties, or put passwords/tokens here. Review the result with Preview effective JSON.

If an old complete manual file hides UI changes, import it into settings, Save and Generate, then move that manual file outside deploy/environments yourself. The generator does not silently remove it.

Custom CI jobs and frontend builds

Additional GitLab jobs belong in deploy/custom/gitlab.yml, included by the generated CI. Do not edit generator-owned .gitlab/admingen.yml or .gitlab-ci.yml. For GitHub, use separately named custom workflows. Frontend Vite extensions belong in admin/custom/vite.ts.

Source CI builds code and resolves the profile from the pipeline's exact commit. Uncommitted changes in the server checkout are not included. The optional protected ADMINGEN_ENVIRONMENT_JSON File variable completely overrides the profile; remove a stale override to use committed UI/custom configuration.

When the server changes

Generate writes local files and does not deploy them. Build/deploy publishes application code. For an established environment, reconfigure applies supported delivery and backup changes; it does not move domains, topology, databases or storage.

Continue with Deployment UI, GitLab CI and Environment commands.