You are here
j1gg3 - Thu, 2019/09/05 - 10:07
Hello,
I have set up mayan-edms but unfortunately I don't know which container path needs to be passed to my host. Mayan documentation says it's the config path folder but within turnkey linux mayan container it seems to be another path.
Thank you in advance.
Forum:
Hi there.
TBH I'm not really clear what you are asking?You mention "container path", but unless you are using our Docker image, then that doesn't really make a lot of sense to me. We don't install Mayan via their docker container.As noted on the Mayan-EDMS appliance page, we install using the "Direct deployment method. And the default storage path is /opt/mayan-edms/media (see the default config file here).On the chance that you are using our Docker container,we construct our containers a little differently to most. They are a "monolithic" container (unlike the way Docker is "normally" used) and contain all the components required (e.g. database, etc) all-in-one.I hope that helps a bit. If I've completely missed the mark on your question, please try again...
Update - Sorry I re-read your post and realised that you ARE using the Docker container... So I've struck out the completely irrelevant parts of my post...
So as per all of our Docker containers, internal storage is used, so our containers aren't really intended to be used in a "stateless" way, as per a "normal" Docker container might be used. You can still use TKLBAM (our built in backup tool) to backup the data if you wish, but if you regularly start/stop the container, that's probably not ideal (would mean a fair bit of traffic downloading your backup everytime you wanted your data back.
It is possible to use Docker in a "non ephemeral" way. By default the data should remain in the specific container that you initially create. However, if you wish to ensure persistent data, then it's probably worth investigating Docker storage. The place to mount the external Docker volume would be /opt/mayan-edms/media. Another option would be to adjust that config (within the running container) and save the changes via 'docker commit' (essentially creating a new base container), then launch a new container (including the setting your just committed). Our documentation is a little scant on details using storage (I probably should improve that when I get some spare cycles), but it may assist you to understand how our containers work a little better!?
Thanks for your prompt answer
Thanks for your prompt answer!
To be honest, I think it doesn't make sense to provide such great and powerful container within docker. As of I have autosuspend enabled on my NAS it is stopping and starting lot of docker container. Due to all data remains within the container / docker volume I'm not able to save also the configuration files.
On each start of the container I need to perform the initialization therefore I think I've missed something. Will try to dig deeper into your documentation, hopefully I'll find a hint.
Cheers!
Sorry for slow follow up...
As per my previous post, either, you need to configure Docker to provide the container with a storage volume - so that the container stores data outside the container (as you would with any other docker container). Or you need to commit the changes, so that they are kept within the container.
Alternatively, if you are already quite familiar with Docker, then perhaps it's worth trying the upstream (i.e. Mayan-EDMS) docker container? I suspect that that is configured more like you would expect a "normal" docker container to be.
PS I fixed a missing link in my previous post too...
Add new comment