Changing settings
Open Project settings and edit the required parameters. Click Save project settings, then Generate → Preview changes. Inspect file changes and Generate.
Save project settings saves only the project description. Updating the application requires generation and its normal build/startup process. Saving does not change the running database or deploy to a server.
Project details and Generation baseline
| Setting | Purpose | Editable here |
|---|---|---|
| Project title | Title in generated-project interfaces | Yes |
| Project name | Technical name | No; fixed at creation |
| Go module | Go module path | No; fixed at creation |
| Generator version | Generation-contract version | No |
| Database driver / schema | Database driver/schema | No |
| Swagger / OpenAPI | Generated API description | Always enabled currently |
For example, set Company Catalog as the user-visible title. Technical company-catalog and Go module remain unchanged.
Deployment settings location
Docker, Production deployment, CI provider and environment profiles are in Deployment in the left menu. See Deployment. Image storage remains in Project settings; server paths/S3 settings are defined in an environment profile.
Image storage
| Option | Storage | Separate configuration |
|---|---|---|
| Local files | Persistent application-local storage | Directory/volume durability and backups |
| Private S3-compatible storage | Private S3-compatible storage | Bucket and runtime credentials |
Image storage selects the generated application's adapter. It does not move existing uploads: switching storage requires a separate data transfer. Formats, limits and variants are configured per image/gallery field.
Unconfirmed save
If the connection fails and save results are unknown, first Refresh saved settings. The editor reads saved configuration and compares it with the draft. Different drafts remain for review; do not blindly repeat save.
Creation-time parameters are covered in CLI: init and editor startup. Use Project settings for supported changes to existing projects.
Source, Archive, Registry and backups are described in Deployment.
General, Storage and Demo tabs
Project settings groups general settings, independent image/file storage and Demo configuration into tabs. Deployment is a separate left-menu module. File storage may use Local files or S3 independently of image storage; see Files.
Demo mode adds a dashboard with Administration, API · Demo (Swagger UI), Data model and Code structure, a generation version and up to three viewing journeys. Ordinary Admin visitors cannot write business data or change their password; Superadmin retains maintenance access. Turning Demo off restores permissions authored in Access. Configure entity Access deliberately; Demo does not replace server authorization.
Appearance is selected with System / Light / Dark; System follows the operating system when no explicit preference is stored. This does not translate the admin UI: content languages are configured separately in Languages.