mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 12:05:58 +03:00
[GH-ISSUE #386] Migrate from Docker to Ubuntu (20.04) VM #306
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#306
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @derAlff on GitHub (Jun 9, 2021).
Original GitHub issue: https://github.com/ciur/papermerge/issues/386
Originally assigned to: @ciur on GitHub.
Hi Eugen,
at the moment, I run Papermerge with your included Docker-Compose file (from your folder in the project). I think, your project is very interesting and I want to use it in future for store all my documents. For that, I have one question and one idea.
For first the question:
If that is possible, then here my idea:
Thank you
Have a nice Day!
@ciur commented on GitHub (Jun 16, 2021):
Regarding your first question:
Yes, it is definitely possible. In general you need to migrate 1. your data directory (called media directory, the place where you files actually live) and 2. your database (sql dump).
For a more general overview of this topic you may have a look at backup section in documentation.
Also, you might be interested in storage structure documentation which explains how/where papermerge saves your documents.
Regarding second point:
Yes, I completely agree that at this point backing up papermerge's data is very nerdy and very command line dependent.
I have that in mind, and I will add in future versions (probably in 2.2) a GUI based backup utility i.e you will be able to import/export data just by clicking in nice user interface.
Thank you for taking your time and opening this ticket!
@lucasff commented on GitHub (Jan 20, 2022):
@necotec I don't agree so much with the idea of having a full blown VM. It's too much resources for a single application. The docker workflow is essentially a VM for Papermerge only. You can use docker volumes and mount them accordingly so you'll always have it ready to start a container without losing your data, config and state.
@derAlff commented on GitHub (Jan 21, 2022):
Jeah, i develop my new infrastructure at the moment. Docker container in portainer.io are really cool. My idea was only for good support and maintenance for the VMs.
I stay on docker containers ;)