When to open Generate
Finish or Save project settings updates the project model; application files may remain unchanged. Open Generate to preview changes before applying them.
Regular workflow
- Preview changes.
- Check Important information: model readiness, warnings, access and routes.
- Expand files in Changes and inspect diffs.
- Fix blockers and Preview again.
- Generate.
- After success, update the running application. Inspect database changes before applying migrations.
Preview is a dry-run, without file writes or a new History entry. Repeat Preview if the model or Force overwrite changes; the earlier result may no longer match generation.
Reading Changes
The summary shows file counts, added/deleted lines, deleted files, blockers and skipped. Rows show path, status and action. Expand for unified diff. The interface indicates when textual comparison is unavailable.
Check API availability after generation in Access and route impact. Pay particular attention to Anonymous and addresses after module moves: external clients may use them.
Conflicts and Force overwrite
| Situation | Action |
|---|---|
| Invalid model/dependency | Return to Content and fix it |
| Manually edited generated file | Review diff and consider moving logic into custom |
| Unrelated file occupies generated path | Resolve ownership conflict |
| Stale Preview | Preview the current model again |
Force overwrite permits replacing manually changed generator-owned files. Use after diff review and preserving needed edits. It bypasses neither model errors nor stale-revision conflicts. Regular Generate must preserve existing custom files. Entity deletion confirms custom archival separately.
Discarding ungenerated changes
Discard ungenerated changes is available when the manifest differs from the last successful Generate. Open it, inspect the diff and confirm only edits you intend to discard.
Discard restores only .admingen/project.yaml. Database, migrations, generated/custom files, lock, history, .env, running application and Git remain unchanged. This undoes model edits since Generate, not the entire application.
After generation
Copy the proposed make dev command and run it from the generated project root. In the Docker workflow, it starts services/applies pending migrations. UI does not run it. This local startup is unavailable when Docker is disabled in Deployment.
If files were written but UI refresh failed, use the offered state refresh. A refresh error does not mean generation changed nothing.