coop-cloud/hedgedoc
coop-cloud
/
hedgedoc
1
1
Fork 2
Code Issues 2 Pull Requests 3 Releases Wiki Activity

fix: use new uploads path #12

Open
decentral1se wants to merge 1 commits from fix-uploads-volume into main
pull from: fix-uploads-volume
merge into: coop-cloud:main
Conversation 3 Commits 1 Files Changed 1 +1 -1
decentral1se commented 2024-04-23 07:23:09 +00:00
Owner
Copy Link

See https://docs.hedgedoc.org/setup/docker/. This means that each on each update of the deployment, the volume for uploads is wiped. I think this was the issue I was running into with using images on https://pad.local-it.org @moritz

See https://docs.hedgedoc.org/setup/docker/. This means that each on each update of the deployment, the volume for uploads is wiped. I think this was the issue I was running into with using images on https://pad.local-it.org @moritz
🚀 1
decentral1se added 1 commit 2024-04-23 07:23:10 +00:00
continuous-integration/drone/pr Build is failing Details
c727320a31
fix: use new uploads path
decentral1se commented 2024-04-23 07:29:47 +00:00
Author
Owner
Copy Link

I just tested this and since the volume name is not removed, docker can seamlessly move the volume contents to another path. So, I think this shouldn't break deployment. In any case, people should back up their stuff before migrating.

I just tested this and since the volume name is not removed, docker can seamlessly move the volume contents to another path. So, I think this shouldn't break deployment. In any case, people should back up their stuff before migrating.
decentral1se commented 2024-04-26 10:50:16 +00:00
Author
Owner
Copy Link

Oh, I did have to run chown -R 10000:65534 .../_data on the volume from the host machine because #11

Oh, I did have to run `chown -R 10000:65534 .../_data` on the volume from the host machine because https://git.coopcloud.tech/coop-cloud/hedgedoc/issues/11
decentral1se requested review from moritz 2024-04-30 19:51:31 +00:00
moritz commented 2024-05-01 11:32:53 +00:00
Member
Copy Link

I haven't tested it yet but it looks fine. I think there should be a release note that informs the people to do a backup before upgrading.

I haven't tested it yet but it looks fine. I think there should be a release note that informs the people to do a backup before upgrading.
Some checks failed
continuous-integration/drone/pr Build is failing
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b fix-uploads-volume main
git pull origin fix-uploads-volume

Step 2:

Merge the changes and update on Gitea.
git checkout main
git merge --no-ff fix-uploads-volume
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
moritz
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/hedgedoc#12
No description provided.
Delete Branch "fix-uploads-volume"

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?