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

Database location #2364

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

Originally created by @Alfly-Alyx on GitHub (Sep 24, 2025).

Description

Hi,

Maybe a bug, maybe a request, maybe neither.

I found 2 locations for the Vikunja Database, the first one at the root of Vikunja and the second one under C:\Windows\System32.

Wouldn't be more convenient to have a single one or have the second one into for example C:\Users*UserName*\ ?

These 2 DB are currently used, as I try to reproducted this on my laptop and delete both, the DB are created again while Vikunja Server is launched.

Vikunja Version

1.0.2-RC

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @Alfly-Alyx on GitHub (Sep 24, 2025). ### Description Hi, Maybe a bug, maybe a request, maybe neither. I found 2 locations for the Vikunja Database, the first one at the root of Vikunja and the second one under C:\Windows\System32. Wouldn't be more convenient to have a single one or have the second one into for example C:\Users\*UserName*\ ? These 2 DB are currently used, as I try to reproducted this on my laptop and delete both, the DB are created again while Vikunja Server is launched. ### Vikunja Version 1.0.2-RC ### 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:04:31 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 24, 2025):

Not sure why this is happening, the location of the database should be only dependent on the configured path.

Does this happen as well if you configure a database path?

@kolaente commented on GitHub (Sep 24, 2025): Not sure why this is happening, the location of the database should be only dependent on the configured path. Does this happen as well if you configure a [database path](https://vikunja.io/docs/config-options/#1-database-path)?
GiteaMirror commented 2026-03-22 14:04:32 -05:00
Author
Owner
Copy Link

@Alfly-Alyx commented on GitHub (Sep 24, 2025):

Yes, I configured ./vikunja.db as path in the database section of the yml

Do you want I share my config.yml in an attached file?

Edit : I've just tried to delete the C:\Windows\System32\vikunja.db on my server. It was locked, I force deleting. Vikunja is still running. I will control if it comes again when I will reboot the server. Previously it did.

@Alfly-Alyx commented on GitHub (Sep 24, 2025): Yes, I configured ./vikunja.db as path in the database section of the yml Do you want I share my config.yml in an attached file? Edit : I've just tried to delete the C:\Windows\System32\vikunja.db on my server. It was locked, I force deleting. Vikunja is still running. I will control if it comes again when I will reboot the server. Previously it did.
GiteaMirror commented 2026-03-22 14:04:32 -05:00
Author
Owner
Copy Link

@Alfly-Alyx commented on GitHub (Sep 24, 2025):

After reboot it comes back (system32 database)

@Alfly-Alyx commented on GitHub (Sep 24, 2025): After reboot it comes back (system32 database)
GiteaMirror commented 2026-03-22 14:04:32 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 9, 2025):

Should be fixed in https://github.com/go-vikunja/vikunja/pull/1616, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Oct 9, 2025): Should be fixed in https://github.com/go-vikunja/vikunja/pull/1616, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](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#2364
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?