Open Deployment in Generator UI. This module controls builds and environment profiles. Model and application capability settings remain in Project settings and Content.
Defaults
Enable Docker and Production deployment. Select CI provider, Server layout, Image delivery and Backups. These values initialize new profiles; they do not silently rewrite existing profiles.
GitLab also exposes Release branch and Automatic deploy here. Keep deployment manual initially. For Build on server, enter Source repository on server, such as /home/deploy/projects/PROJECT_NAME: an existing VPS Git repository accessible by the deployment user.
Create or import an environment
Use + Create beside the Environment selector. In the dialog, choose a new profile or complete JSON import, enter a name such as local, test or production, and choose the preset. The new profile joins the list but remains unsaved until Save.
You can keep several profiles and edit the selected one. --env selects a profile name, not a project name or placement preset. Applications sharing a host need distinct runtime directories, ports and domains.
Fill the profile tabs
| Setting | Value |
|---|---|
| Runtime directory | Persistent data and environment state; absolute on a server |
| Domains / TLS | Real admin/API domains and contact email for built-in TLS |
| Delivery | Source, Archive or Registry |
| Backend SSH target | deploy@YOUR_SERVER_HOST for CI/remote operations |
| Ingress | Standalone, or External with a dedicated loopback port behind host Nginx |
| Media / Files | Parameters for the image/file storage selected in Project settings |
| Backup | None, Local or S3, independently of working storage |
| Allowed HTTPS origins | Exact browser application origins |
Source supports one server and CI None or GitLab. Manual Source does not require SSH to itself; Source CI requires the VPS SSH target. Archive/Registry support single or split hosts. Registry needs complete backend/admin/ops repositories; credentials remain outside UI.
External ingress supports ordinary projects sharing host Nginx, independently of Demo mode. The host serves public HTTPS and each frontend publishes its own loopback port.
Save and inspect
Use Save deployment settings, then Generate. This writes deploy/generated/environments/ENV_NAME.json and seeds deploy/custom/environments/ENV_NAME.json. Replace ENV_NAME with the profile name. No copy into deploy/environments is needed.
Preview effective JSON shows the resolved custom overlay. A complete manual profile takes priority; the UI identifies the configuration source and overridden values. See Custom deployment.
Save/Generate do not change the VPS. A new installation uses Provision/Deploy; ordinary code updates use Deploy. Supported changes to an established environment's delivery/backup settings require explicit reconfigure.