Skip to content

Vikunja: The Third Board and Why It Exists

What is Vikunja?

Vikunja is a local task board accessible at http://127.0.0.1:3456 on the greatroom computer. It acts as the third board in our fleet system alongside Jira (where work is managed) and BOARD.md (the board stored inside git repos).

These documents exist because many team members and automated tools didn't know Vikunja existed or how it fits into our workflow.

Why Does It Exist?

Vikunja provides a fast, visual, local interface to view tasks without needing external internet connectivity or parsing raw text files. It acts as a mirror for convenience and redundancy.

How It Works

  • Read-Only Mirror: Vikunja automatically copies data from Jira. It does not store any unique information of its own.
  • Automated Sync: A background task named FleetBoardSync runs on the greatroom computer to keep Vikunja up to date.
  • No Hand Edits: Do not create or edit tickets directly in Vikunja. Always make changes in Jira.
  • Single Host: The sync process runs strictly on the greatroom computer. Never run sync scripts from other PCs.

Security & Projects

  • Access requires a secret key file stored at ~/.fleet-secrets/vikunja.json. Never display or print this key.
  • Key project areas in Vikunja:
  • Project 7: Fleet (FLT)
  • Project 8: WorkWingman (WING)

What To Do If Vikunja Breaks

Because Vikunja contains no unique data, restoring it is straightforward: 1. Rebuild it from Jira at any time on any computer by running: pwsh -File fleet-harness/ops/board-sync/Rehydrate-Vikunja.ps1 -FromJira 2. Warning on Database Dumps: Avoid using database dump files (-FromDump) to fix issues. The restore script checks the backup file first, then replaces the database — still a destructive operation. Rebuilding from Jira (-FromJira) is always the safer choice.