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 13 Packages Projects Releases 10 Wiki Activity

Grist update removes user data #505

New Issue
Closed
opened 2026-02-04 19:22:12 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-04 19:22:12 +03:00
Owner
Copy Link

Originally created by @wms8688 on GitHub (Feb 15, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Grist

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/grist.sh)"

📝 Provide a clear and concise description of the issue.

After running the update, all user data is removed essentially making it a clean install of the new version.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/grist.sh)"
Click OK

❌ Paste the full error output (if available).

Update completes successfully, no errors. The installation appears to function normally minus all user data.

🖼️ Additional context (optional).

No response

Originally created by @wms8688 on GitHub (Feb 15, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Grist ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/grist.sh)" ### 📝 Provide a clear and concise description of the issue. After running the update, all user data is removed essentially making it a clean install of the new version. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/grist.sh)" Click OK ### ❌ Paste the full error output (if available). Update completes successfully, no errors. The installation appears to function normally minus all user data. ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 19:22:12 +03:00
OVERLORD commented 2026-02-04 19:22:32 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 15, 2025):

Can you give an information where Userdata is stored ?

@MickLesk commented on GitHub (Feb 15, 2025): Can you give an information where Userdata is stored ?
OVERLORD commented 2026-02-04 19:22:48 +03:00
Author
Owner
Copy Link

@wms8688 commented on GitHub (Feb 15, 2025):

Looks like /opt/grist/docs, /opt/grist/grist-sessions.db and /opt/grist/landing.db. Not sure if there are any others.

@wms8688 commented on GitHub (Feb 15, 2025): Looks like /opt/grist/docs, /opt/grist/grist-sessions.db and /opt/grist/landing.db. Not sure if there are any others.
OVERLORD commented 2026-02-04 19:22:59 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 15, 2025):

@cfurrow / @michelroegl-brunner

@MickLesk commented on GitHub (Feb 15, 2025): @cfurrow / @michelroegl-brunner
OVERLORD commented 2026-02-04 19:23:03 +03:00
Author
Owner
Copy Link

@cfurrow commented on GitHub (Feb 16, 2025):

Ah, yup! My mistake. I appreciate the details!

I will work on a PR to fix this by copying those files from the /opt/grist_bak to the /opt/grist after the update is fetched.

@cfurrow commented on GitHub (Feb 16, 2025): Ah, yup! My mistake. I appreciate the details! I will work on a PR to fix this by copying those files from the `/opt/grist_bak` to the `/opt/grist` after the update is fetched.
OVERLORD commented 2026-02-04 19:23:18 +03:00
Author
Owner
Copy Link

@cfurrow commented on GitHub (Feb 16, 2025):

Update: I'll need to dig into this a bit more.

Simply copying the files during update has not restored previous documents like I'd hoped.

# ct/grist.sh
#...snip
    cp grist_bak/.env grist/.env || true
    cp -r grist_bak/docs/* grist/docs/ || true
    cp grist_bak/grist-sessions.db grist/grist-sessions.db || true
    cp grist_bak/landing.db grist/landing.db || true
#...snip

The files are copied over, but they are not being read. Launching grist does not seem to load the previous documents. The session database seems to be working, because my previous login worked after the update.

@cfurrow commented on GitHub (Feb 16, 2025): **Update**: I'll need to dig into this a bit more. Simply copying the files during update has not restored previous documents like I'd hoped. ```sh # ct/grist.sh #...snip cp grist_bak/.env grist/.env || true cp -r grist_bak/docs/* grist/docs/ || true cp grist_bak/grist-sessions.db grist/grist-sessions.db || true cp grist_bak/landing.db grist/landing.db || true #...snip ``` The files are copied over, but they are not being read. Launching `grist` does not seem to load the previous documents. The session database seems to be working, because my previous login worked after the update.
OVERLORD commented 2026-02-04 19:23:23 +03:00
Author
Owner
Copy Link

@cfurrow commented on GitHub (Feb 16, 2025):

Alright, I may have simply had a typo in my previous fix attempts, because when I did it all again, it worked.

Fix PR: https://github.com/community-scripts/ProxmoxVE/pull/2428

My repro steps:

  • stop the grist service
  • backup the /opt/grist directory manually by moving it to /opt/grist_bak
  • download a previous version of Grist (I was working with v1.3.2, latest version was v1.4.0)
  • extract the release to /opt/grist
  • copy the user files from /opt/grist_bak to /opt/grist
  • run the setup scripts:
    • yarn install
    • yarn run build:prod
    • yarn run install:python
  • start the grist service
  • create 2 new Grist documents in the web UI by importing a couple test CSV files
  • go to step 1, but download and install v1.4.0

My "updated" install of v1.4.0 had the previous 2 Grist documents restored.

@cfurrow commented on GitHub (Feb 16, 2025): Alright, I may have simply had a typo in my previous fix attempts, because when I did it all again, it worked. Fix PR: https://github.com/community-scripts/ProxmoxVE/pull/2428 My repro steps: - stop the grist service - backup the `/opt/grist` directory manually by moving it to `/opt/grist_bak` - download a previous version of Grist (I was working with v1.3.2, latest version was v1.4.0) - extract the release to `/opt/grist` - copy the user files from `/opt/grist_bak` to `/opt/grist` - run the setup scripts: - `yarn install` - `yarn run build:prod` - `yarn run install:python` - start the grist service - create 2 new Grist documents in the web UI by importing a couple test CSV files - go to step 1, but download and install v1.4.0 My "updated" install of v1.4.0 had the previous 2 Grist documents restored.
OVERLORD commented 2026-02-04 19:23:29 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Feb 16, 2025):

Merged.

@michelroegl-brunner commented on GitHub (Feb 16, 2025): Merged.
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#505
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?