oops, left out a step, initializing the container... here is better run through...
create a mayan volume for the data: # docker volume create --name mayan_media --opt type=none --opt device=/ path/to/data/share --opt o=bind inspect the volume to make sure it was created: # docker volume inspect mayan_media initialize the container # docker run --rm -v mayan_media:/var/lib/mayan -v mayan_settings:/etc/ mayan mayanedms/mayanedms mayan:init launch mayan as normal: # docker run -d --name mayan-edms --restart=always -p 80:80 -v mayan_data:/var/lib/mayan -v /path/to/watch/folder:/path/to/watch/folder - v /path/to/staging/folder:/path/to/staging/folder mayanedms/mayanedms: 2.6.4-3 On Sun, 28 Jan 2018 22:57:16 +0000, Douglas Van Es wrote: > i did something similar for my docker set up. mayan doesn't run on a vm > in my case, but what i had to do to get my mayan data stored outside of > the container was create a mayan volume first, then launch mayan. > > # docker volume create --name mayan_media --opt type=none --opt device=/ > path/to/data/share --opt o=bind > > then i inspected the volume to make sure it was created: > > # docker volume inspect mayan_media > > looked good, so i launched mayan as normal: > > # docker run -d --name mayan-edms --restart=always -p 80:80 -v > mayan_data:/var/lib/mayan -v /path/to/watch/folder:/path/to/watch/folder > - > v /path/to/staging/folder:/path/to/staging/folder mayanedms/mayanedms: > 2.6.4-3 > > let me know if this helps...i can't remember where i found the info on > this, i've been looking through the mayan documentation and don't see > it. but i found it somehow originally. > > doug > > > > On Sun, 28 Jan 2018 11:51:09 -0800, Ray Hendricks wrote: > >> I've given up on the bare metal install. Too many moving parts for me >> to feel like it's a robust enough system to rebuild if (when) a failure >> happens. >> >> I've followed this >> https://www.mayan-edms.com/post/deploy-mayan-docker-mysql/ and have it >> up an running on a Ubuntu VM. >> >> I set he docker up with this command: "sudo docker run -d --name >> mayan-edms --restart=always --env-file /home/ray/envfile -v >> /media/vintage:/media/vintage -v mayan_data:/var/lib/mayan --net=mayan >> -p 80:80 mayanedms/mayanedms:2.6.4-3" >> >> /media/vintage" is a CIFS mount on the VM that is mounted with the >> following fstab: "//adama/vintage /media/vintage cifs >> credentials=/home/ > ray/.smbcredentials,iocharset=utf8,sec=ntlm,file_mode=0777,dir_mode=0777 >> 0 0" >> >> I tested successfully that I can read/write from both the VM and from >> within the container. >> >> Now what I'm trying to do is get the data storage to be on the server >> instead of inside the VM. >> >> Inside the VM is a directory "/var/lib/docker/volumes/" where both the >> "mayan_data" and "myswl_data" are stored. - This is good, the data is >> persistent and outside the container. >> >> I've changed the local.py in the >> "/var/lib/docker/volumes/mayan_data/_data/settings/" and increased the >> search results that are returned to be 500. I restarted the container >> and everything works and the SEARCH_LIMIT has been updated. - GREAT! >> >> Now I tried changing STORAGE_FILESTORAGE_LOCATION = >> "/media/vintage/mayan" >> and it fails. The container just reboots over and over. >> >> How can I get Mayan to use /media/vintage/mayan as the document storage >> so i can have the data outside the VM? >> >> I have a watch folder set up on /media/vintage and it works great. >> >> >> >> -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
