github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

SQLite absolute database path ignored in 1.0.0, only relative path works #2513

New Issue
Closed
opened 2026-03-22 14:10:00 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-22 14:10:00 -05:00
Owner
Copy Link

Originally created by @NixNivis on GitHub (Feb 2, 2026).

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

When configuring an absolute path for the SQLite database in config.yml, Vikunja 1.0.0 ignores it and uses the default path instead. Only relative paths work correctly.
Environment:

Vikunja version: 1.0.0
Database: SQLite
Installation method: .deb package on Debian Trixie

Configuration (does NOT work):

database:
  type: sqlite
  path: "/var/lib/vikunja/vikunja.db"  # Absolute path

Result:

level=INFO msg="Using SQLite database at: /opt/vikunja/vikunja.db"

Config is read (confirmed via logs), but the absolute path is ignored.
Workaround (works):

service:
  rootpath: "/var/lib/vikunja/"
database:
  type: sqlite
  path: "vikunja.db"  # Relative path

Result:

level=INFO msg="Using SQLite database at: /var/lib/vikunja/vikunja.db"

Expected behavior:
According to the documentation, absolute paths should work: "Can be an absolute path or relative path."

Vikunja Version

1.0.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @NixNivis on GitHub (Feb 2, 2026). ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description When configuring an absolute path for the SQLite database in config.yml, Vikunja 1.0.0 ignores it and uses the default path instead. Only relative paths work correctly. Environment: Vikunja version: 1.0.0 Database: SQLite Installation method: .deb package on Debian Trixie Configuration (does NOT work): ```yaml database: type: sqlite path: "/var/lib/vikunja/vikunja.db" # Absolute path ``` **Result:** ``` level=INFO msg="Using SQLite database at: /opt/vikunja/vikunja.db" ``` Config is read (confirmed via logs), but the absolute path is ignored. Workaround (works): ```yaml service: rootpath: "/var/lib/vikunja/" database: type: sqlite path: "vikunja.db" # Relative path ``` **Result:** ``` level=INFO msg="Using SQLite database at: /var/lib/vikunja/vikunja.db" ``` Expected behavior: According to [the documentation](https://vikunja.io/docs/config-options/#1-database-path), absolute paths should work: "Can be an absolute path or relative path." ### Vikunja Version 1.0.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 14:10:01 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 4, 2026):

Can you verify the correct config file is loaded? There should be a log message about it when Vikunja is started.

@kolaente commented on GitHub (Feb 4, 2026): Can you verify the correct config file is loaded? There should be a log message about it when Vikunja is started.
GiteaMirror commented 2026-03-22 14:10:02 -05:00
Author
Owner
Copy Link

@NixNivis commented on GitHub (Feb 4, 2026):

Correct config file is loaded, which does have the correct absolute path set. Despite that, during startup the default path is used - I have rolled back to 0.24.6 due to the other bug I experienced during migration, so I cannot test any further, but I still have all logs.

Feb 02 19:54:15 <correct_domain> systemd[1]: Started vikunja.service - Vikunja.
Feb 02 19:54:15 <correct_domain> vikunja[865400]: time=2026-02-02T19:54:15.530+01:00 level=INFO msg="Using config file: /etc/vikunja/config.yml"
Feb 02 19:54:15 <correct_domain> vikunja[865400]: time=2026-02-02T19:54:15.533+01:00 level=INFO msg="Running migrations…"
Feb 02 19:54:15 <correct_domain> vikunja[865400]: time=2026-02-02T19:54:15.533+01:00 level=INFO msg="Using SQLite database at: /opt/vikunja/vikunja.db"
Feb 02 19:54:15 <correct_domain> vikunja[865400]: time=2026-02-02T19:54:15.533+01:00 level=ERROR msg="Could not connect to db: could not open database file [uid=996, gid=995]: open /opt/vikunja/vikunja.db: read-only file system"

with config

 service:
  rootpath: "/var/lib/vikunja/"
  publicurl: "https://<correct_domain>"
 database:
  path: "/var/lib/vikunja/vikunja.db"
@NixNivis commented on GitHub (Feb 4, 2026): Correct config file is loaded, which does have the correct absolute path set. Despite that, during startup the default path is used - I have rolled back to 0.24.6 due to the other [bug](https://github.com/go-vikunja/vikunja/issues/2188) I experienced during migration, so I cannot test any further, but I still have all logs. ```bash Feb 02 19:54:15 <correct_domain> systemd[1]: Started vikunja.service - Vikunja. Feb 02 19:54:15 <correct_domain> vikunja[865400]: time=2026-02-02T19:54:15.530+01:00 level=INFO msg="Using config file: /etc/vikunja/config.yml" Feb 02 19:54:15 <correct_domain> vikunja[865400]: time=2026-02-02T19:54:15.533+01:00 level=INFO msg="Running migrations…" Feb 02 19:54:15 <correct_domain> vikunja[865400]: time=2026-02-02T19:54:15.533+01:00 level=INFO msg="Using SQLite database at: /opt/vikunja/vikunja.db" Feb 02 19:54:15 <correct_domain> vikunja[865400]: time=2026-02-02T19:54:15.533+01:00 level=ERROR msg="Could not connect to db: could not open database file [uid=996, gid=995]: open /opt/vikunja/vikunja.db: read-only file system" ``` with config ```yaml service: rootpath: "/var/lib/vikunja/" publicurl: "https://<correct_domain>" database: path: "/var/lib/vikunja/vikunja.db" ```
GiteaMirror commented 2026-03-22 14:10:02 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 8, 2026):

I've added a bunch of tests and potential fixes around this in https://github.com/go-vikunja/vikunja/pull/2193 - please check with the next unstable build once that PR is merged.

@kolaente commented on GitHub (Feb 8, 2026): I've added a bunch of tests and potential fixes around this in https://github.com/go-vikunja/vikunja/pull/2193 - please check with the next unstable build once that PR is merged.
GiteaMirror commented 2026-03-22 14:10:03 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Feb 8, 2026):

This issue has been fixed in #2193, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Feb 8, 2026): This issue has been fixed in #2193, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2513
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?