36 lines
2.6 KiB
Markdown
36 lines
2.6 KiB
Markdown
# Bundle 1 — development database audit
|
|
|
|
Audited 2026-09-27 against the configured local PostgreSQL development database, `guilan_ace_local` (`127.0.0.1:5432`). This is the development database the owner authorized in place of staging. No staging or production database was accessed.
|
|
|
|
## Migration and data state
|
|
|
|
All content migrations are applied: `0001_initial`, `0002_alter_siteidentity_options`, `0003_content_groups`, `0004_direct_edit_content`, and `0005_seed_current_website_copy`.
|
|
|
|
Before running the mock-content command, the current editable tables contained one site record, one Home record, one About record, two listing records, and nine About items. There were no image references or missing media files. Django admin change history contained two changes for Home and none for Site, About, Events, or Blog.
|
|
|
|
The legacy revision tables were empty: zero SiteIdentity, SiteRevision, EditorialPage, PageRevision, PageSection, MediaAsset, or PublicationAudit rows. Their model definitions, database tables, and historical permission records remain from the applied migration history; no migration or table cleanup was performed.
|
|
|
|
## Permission state
|
|
|
|
The database has one staff account, which is also the only superuser. The `content_editor` and `content_publisher` groups each have zero members. No user has a direct content-model permission assignment. The two legacy groups contain standard content-model change permissions plus old workflow permission records; they grant access to no account in this database.
|
|
|
|
This is an environment-specific snapshot. Staff account assignments in staging or production remain part of the release audit.
|
|
|
|
## Mock-content command
|
|
|
|
The owner approved mock copy and empty optional images for initial content. The command was first reviewed with:
|
|
|
|
```sh
|
|
python manage.py seed_mock_content --dry-run --database default
|
|
```
|
|
|
|
The dry run proposed replacing Site, About, Events, and Blog, and skipped Home because it has Django admin change history. The command was then run against the same development database:
|
|
|
|
```sh
|
|
python manage.py seed_mock_content --database default
|
|
```
|
|
|
|
It updated those four records, preserved Home, and replaced the untouched About items with six mock items. A read-only follow-up query confirmed the expected mock records, both listing titles and SEO titles, six About items, no image references, and the preserved Home row with its two admin changes. The command did not modify any migration.
|
|
|
|
The owner has reviewed and approved the mock content and the development database result. Production initialization remains subject to the release gate.
|