Dashboard purpose
Dashboard summarizes the current project: defined entities and last generation. Here you manage application structure; articles, products and other records are edited in the generated admin.
Connecting to the local generator
Start the local generator and open its printed address. UI creates a session with this process automatically; generated-application credentials are unnecessary. The session lasts eight hours and belongs only to this process.
If unavailable, Retry after the process recovers. For an expired session, reopen the running generator's UI. Origin errors often indicate a different address: use Admingen's printed local address rather than an arbitrary domain or another machine.
Counters
| Card | Meaning |
|---|---|
| Entities | Model entity count |
| Fields | Declared field count |
| Relations | Declared relationship count |
| History entries | Generation-history record count |
Counters describe the model, not database records. Entities increases after saving a new entity; Generate is still needed for its form and API.
Project summary
Check title, database/schema, API format, backend/frontend and UI mode. The entity list marks virtual entities Virtual. When working with multiple projects, check this summary first to avoid editing the wrong model.
Last generation
Last generation shows the last recorded run's time, action, changed-file/operation counts and generator version. No generation history yet is normal for a new project. Preview shows changes without creating an applied-generation History record.
Next steps
| Task | Section |
|---|---|
| Change interface title or image storage | Project settings |
| Configure Docker, CI and environments | Deployment |
| Add entities, fields or relationships | Content |
| Preview/apply file changes | Generate |
| Inspect earlier generations | History |
The same model can also be edited through CLI. Project creation and local UI startup are in CLI interface. Dashboard itself does not start application servers.