You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(db): restore base directory-creation semantics
Creating the parent of every resolved path was too broad. An absolute or
rootpath-relative database.path with a missing parent used to fail loudly and
create nothing; it silently created a 0700 tree and an empty database instead —
so a typo'd or unmounted path looked like data loss. The scratch Docker image
sets VIKUNJA_DATABASE_PATH=/db/vikunja.db with no /db, so an unmounted volume
would have written to the container layer.
It also killed the rootpath fallback for an unwritable user data directory,
turning a warn-and-continue into a refusal to start — upgrade-breaking for
containers whose service user has an unwritable HOME.
Creation moves back inside the injected getter: resolution passes
existingUserDataDir (stat only), the engine passes createdUserDataDir. Both fall
back to rootpath on failure, so they agree once the directory exists.
0 commit comments