Drop the leftover vikunja database #60

Open
opened 2026-11-10 19:47:06 +00:00 by martin · 0 comments
Owner

Summary

The vikunja service was removed, but its PostgreSQL database (about 10 MB) is still present on nidaros. It no longer receives connections and serves no purpose.

Context

  • Service removal: commit 2779110 ("Remove vikunja service").
  • vikunja is already on collation 2.42, so it is not part of the collation repair work.
  • No current configuration references the database.

Scope

  • Confirm no consumer or backup process still needs the data.
  • Drop the database.

Acceptance criteria

  • No service, backup, or monitoring configuration references the vikunja database.
  • The database is dropped and the change is noted in the commit message.
## Summary The vikunja service was removed, but its PostgreSQL database (about 10 MB) is still present on nidaros. It no longer receives connections and serves no purpose. ## Context - Service removal: commit `2779110` ("Remove vikunja service"). - `vikunja` is already on collation 2.42, so it is not part of the collation repair work. - No current configuration references the database. ## Scope - Confirm no consumer or backup process still needs the data. - Drop the database. ## Acceptance criteria - [ ] No service, backup, or monitoring configuration references the vikunja database. - [ ] The database is dropped and the change is noted in the commit message.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Personal/nixos-configuration#60
No description provided.