Check the section "Customizing the image" here: https://hub.docker.com/r/mayanedms/mayanedms/
It is not the easiest thing to do but it is the way Docker images are officially customized. However, after the next version, I plan to work on finding ways to customize the image without having to rebuild a new image. One idea I want to try is providing an environment variable called MAYAN_PIP_PACKAGES or similar that contains a comma delimited list of packages to download and install from the web. The disadvantage of this approach is that the installed packages are not persistent and need to be downloaded and installed every time the image starts. Also planning on trying something like MAYAN_APT_PACKAGES too to allow installing Ubuntu packages like extra OCR language packs at runtime. Docker provides a command called "commit" which could be the answer to the non persistent issue. These are all untested ideas at the moment and for now the only official way to customize an image is the one provided in the link above. On Wednesday, June 21, 2017 at 3:42:30 PM UTC-4, Douglas Van Es wrote: > > yes any tips on installing an extension into a mayan docker container > roberto? > > thanks again matthias! i really appreciate the help > > doug > > On Mon, 19 Jun 2017 13:25:34 +0200, Matthias Löblich wrote: > > > Hi Douglas, > > I have not done any stuff on Docker with the document_analyzer, but if I > > look into the mayan docker file: > > > > https://gitlab.com/mayan-edms/mayan-edms-docker/blob/master/Dockerfile > > > > It is using ubuntu:16.04 image and installing mayan by "RUN pip install > > mayan-edms==2.3". So I guess mayan will be installed in sitepackages. > > > > How to find the sitepackages-folder: > > > > MY Laptop is an: > > ~$ lsb_release -a No LSB modules are available. > > Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: > > 16.04 Codename: xenial > > > > Start python: > > ~$ python Python 2.7.12 (default, Nov 19 2016, 06:48:10) > > [GCC 5.4.0 20160609] on linux2 Type "help", "copyright", "credits" or > > "license" for more information. > > > > Run: > >>>> import site; site.getsitepackages() > > ['/usr/local/lib/python2.7/dist-packages', > > '/usr/lib/python2.7/dist-packages'] > >>>> > >>>> > > > > But this might be a good question for Roberto: How to integrate an > > Extension in to the mayan docker image. > > > > > > br Matthias > > > > > > > > > > 2017-06-15 19:18 GMT+02:00 Douglas Van Es > > <[email protected]>: > > > >> wow thank you matthias, this looks like it may work for me. > >> > >> i have a couple of questions based on the docs at the github site, and > >> am wondering if you could help me out with them. what would my mayan > >> root folder be on an install using docker? i've looked around > >> /var/lib/docker and can't quite figure out the correct place to create > >> a link to document_analyzer... > >> > >> would it be something like this: > >> /var/lib/docker/aufs/mnt/HASHEDNAME/usr/ local/bin/ ? i don't have an > >> apps folder in there. > >> > >> i've found local.py in /var/lib/docker/volumes/mayan_settings/_data/ > >> and so will be able to edit that file to include document_analyser in > >> the list of installed apps, but can't find a /mymayanroot/apps folder. > >> > >> will the migrations step shown on the git page be the same for a docker > >> install? eg: mayan-edms.py migrate ? i suppose i would execute that > >> from / > >> var/lib/docker/aufs/mnt/HASHEDNAME/usr/local/bin/ right? > >> > >> thank you for the help so far! > >> > >> > >> > >> On Fri, 09 Jun 2017 01:42:16 -0700, Matthias Löblich wrote: > >> > >> > Hi, > >> > it did an Extension for mayan called /document_analyzer > >> > > >> > https://gitlab.com/mayan-edms/document_analyzer > >> > > >> > The idea behind is to analyze a document and store the result in an > >> > generic way (similar to metadata structure). At the moment there are > >> > two "analyzers" implemented. One which reads the exif data and one > >> > where you can configure regular expressions which are used to parse > >> > the ocr result of an document. > >> > If you are able to write an regular expression to parse the invoice > >> > number (be aware that the ocr qualtity is very important !) you can > >> > use the extension to store the invoice number in a metadata like > >> > structure. You can also configure an mayan index on it. > >> > > >> > br Matthias > >> > > >> > > >> > Am Donnerstag, 8. Juni 2017 22:54:09 UTC+2 schrieb Douglas Van Es: > >> >> > >> >> > >> >> if i crack this or hear from anyone at mayan i'll be sure to let you > >> >> know. > >> >> > >> >> i'm in the same boat, if i can be sure mayan is going to work for us > >> >> a support plan is in our future as well. > >> >> > >> >> > >> >> > >> >> On Tue, 06 Jun 2017 17:13:08 -0700, David Kornahrens wrote: > >> >> > >> >> > I'm currently trying to walk myself through the program as well. > >> >> > We really see the potential here, but help doesn't come quick. > >> >> > I'm interested in getting a support plan, but not if the support > >> >> > speed doesn't increase. > >> >> > > >> >> > Roberto has answered a few questions, but it's more of a waiting > >> >> > game really. I posted some issues in the GitLab repository, but > >> >> > nothing on that yet either. Let me known if you figure it out, we > >> >> > are looking into the same thing. > >> >> > >> >> > >> >> > >> >> > >> > >> -- > >> > >> --- > >> You received this message because you are subscribed to a topic in the > >> Google Groups "Mayan EDMS" group. > >> To unsubscribe from this topic, visit https://groups.google.com/d/ > >> topic/mayan-edms/6P1AqlvNjWQ/unsubscribe. > >> To unsubscribe from this group and all its topics, send an email to > >> mayan-edms+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/ > [email protected] > >> For more options, visit https://groups.google.com/d/optout. > >> > > > -- --- 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.
