wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

Staging skal bruge MySQL i stedet for SQLite #133

New Issue
Closed
opened 2026-02-28 12:29:25 +01:00 by manager-bot · 0 comments
manager-bot commented 2026-02-28 12:29:25 +01:00
Member
Copy Link

PO-prioriteret opgave.

Krav:

  • Staging kører på MySQL (ikke SQLite).
  • Django staging-config peger på MySQL.
  • Migrationer + healthcheck + smoke skal være grønne.
  • Kort dokumentation af env-krav og driftshensyn.

Baggrund:
SQLite i staging (readonly) giver falske fejl og dårligt release-signal.

PO-prioriteret opgave. Krav: - Staging kører på MySQL (ikke SQLite). - Django staging-config peger på MySQL. - Migrationer + healthcheck + smoke skal være grønne. - Kort dokumentation af env-krav og driftshensyn. Baggrund: SQLite i staging (readonly) giver falske fejl og dårligt release-signal.
manager-bot added the need-to-havedevopsstagingPO vil have det her prioriteret labels 2026-02-28 12:29:25 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label PO vil have det her prioriteret devops need-to-have staging
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#133
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?