starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Vikunja Script Update Dropped Config #137

New Issue
Closed
opened 2026-02-04 16:47:10 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-04 16:47:10 +03:00
Owner
Copy Link

Originally created by @xijio on GitHub (Dec 5, 2024).

Originally assigned to: @michelroegl-brunner on GitHub.

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

I updated vikunja using the update command and it delete my config. I had to restore from backup.

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

Type update.

restart lxc
try to login, can't user doesn't exist
rollback

Originally created by @xijio on GitHub (Dec 5, 2024). Originally assigned to: @michelroegl-brunner on GitHub. ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. I updated vikunja using the update command and it delete my config. I had to restore from backup. ### What settings are you currently utilizing? - [X] Default Settings - [ ] Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. Type update. restart lxc try to login, can't user doesn't exist rollback
OVERLORD added the bug label 2026-02-04 16:47:10 +03:00
OVERLORD commented 2026-02-04 16:47:31 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Dec 5, 2024):

It seems the update function is deleting everything under /opt/

cd /opt
rm -rf /opt/*

I take a look at that later today @MickLesk .

@michelroegl-brunner commented on GitHub (Dec 5, 2024): It seems the update function is deleting everything under /opt/ ``` cd /opt rm -rf /opt/* ``` I take a look at that later today @MickLesk .
OVERLORD commented 2026-02-04 16:47:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 5, 2024):

there are no files there. thats an AIO Package

@MickLesk commented on GitHub (Dec 5, 2024): there are no files there. thats an AIO Package
OVERLORD commented 2026-02-04 16:47:48 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Dec 5, 2024):

Looks like db is stored in /etc/vikunja/vikunja.db and files stored in /etc/vikunja/files, not sure why users would be deleted in this update. Vikunja states they do necessary migrations on binary restart https://vikunja.io/docs/installing/#updating

@havardthom commented on GitHub (Dec 5, 2024): Looks like db is stored in `/etc/vikunja/vikunja.db` and files stored in `/etc/vikunja/files`, not sure why users would be deleted in this update. Vikunja states they do necessary migrations on binary restart https://vikunja.io/docs/installing/#updating
OVERLORD commented 2026-02-04 16:47:54 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Dec 5, 2024):

Ah probably an old install before this change 9795d41d39

@havardthom commented on GitHub (Dec 5, 2024): Ah probably an old install before this change https://github.com/community-scripts/ProxmoxVE/commit/9795d41d398adf8b8086f2bd19da6bb7d9013eda
OVERLORD commented 2026-02-04 16:47:57 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Dec 5, 2024):

Yes, i´m testing this right now and i can not reproduce the issue so far.

@havardthom yep, seems to be an older install then.

@michelroegl-brunner commented on GitHub (Dec 5, 2024): Yes, i´m testing this right now and i can not reproduce the issue so far. @havardthom yep, seems to be an older install then.
OVERLORD commented 2026-02-04 16:48:02 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Dec 5, 2024):

Probably best not to remove whole opt folder, for people with old config before that change

@havardthom commented on GitHub (Dec 5, 2024): Probably best not to remove whole opt folder, for people with old config before that change
OVERLORD commented 2026-02-04 16:48:18 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Dec 5, 2024):

Probably best not to remove whole opt folder, for people with old config before that change

There is a file create during install under /opt/vikunja but it doese not look like it is related to the update data loss problem.

If you want to, i can change the script to not delete the folder an do a PR.

@michelroegl-brunner commented on GitHub (Dec 5, 2024): > Probably best not to remove whole opt folder, for people with old config before that change There is a file create during install under /opt/vikunja but it doese not look like it is related to the update data loss problem. If you want to, i can change the script to not delete the folder an do a PR.
OVERLORD commented 2026-02-04 16:48:21 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Dec 5, 2024):

Probably best not to remove whole opt folder, for people with old config before that change

There is a file create during install under /opt/vikunja but it doese not look like it is related to the update data loss problem.

If you want to, i can change the script to not delete the folder an do a PR.

Sure, just delete/overwrite the old binary instead of the whole folder 👍

@havardthom commented on GitHub (Dec 5, 2024): > > Probably best not to remove whole opt folder, for people with old config before that change > > There is a file create during install under /opt/vikunja but it doese not look like it is related to the update data loss problem. > > If you want to, i can change the script to not delete the folder an do a PR. Sure, just delete/overwrite the old binary instead of the whole folder :+1:
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#137
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?