Implemented fix and opened PR for blocker.
What changed:
- Removed tracked `db.sqlite3` from repository so release/deploy source archives do not ship a stale SQLite DB artifact.
- This removes the root-owned sqlite file path that caused `attempt to write a readonly database` during staging `migrate`.
Checks run:
- `bash -n infra/staging/deploy_staging.sh`
- `test -z "$(git ls-files db.sqlite3)"`
Artifacts:
- Commit: `12fc12f955618b895f14e2109e24409206bc2fd6`
- PR: #135 (`fix/staging-sqlite-artifact-131` -> `main`)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Oprettet ifm. issue #90 release readiness.
Deploy kommando:
./infra/staging/deploy_staging.sh mainFejl:
django.db.utils.OperationalError: attempt to write a readonly databaseObservationer i CT 143:
/opt/wpp-staging/app/db.sqlite3ejes afroot:root(mode 664)runuser -u wppDette blokerer staging deploy af seneste main.
Implemented fix and opened PR for blocker.
What changed:
db.sqlite3from repository so release/deploy source archives do not ship a stale SQLite DB artifact.attempt to write a readonly databaseduring stagingmigrate.Checks run:
bash -n infra/staging/deploy_staging.shtest -z "$(git ls-files db.sqlite3)"Artifacts:
12fc12f955618b895f14e2109e24409206bc2fd6fix/staging-sqlite-artifact-131->main)