Just as a hint, I started to build me a small Docker container for running SeedDMS. However, I intended it to not run standalone, but it's just a minimal "php:apache" container with some stuff added (apt-get -y install zlib1g-dev imagemagick libpng-dev poppler-utils catdoc libpq-dev id3; docker-php-ext-install gd pdo pdo_pgsql) and a bit of config:
SeedDMS is extracted to the ./seeddms_html directory, it's config file modified to use the host's PostgreSQL database and all documents are also in a separate docker mount as seen above.
This should separate SeedDMS, the Apache/PHP setup, and the actual data.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks a lot for this! I just started to explore this :)
Is your Dockerfile somewhere around? Or the Docker hub documentation? I'd drop a few patches to make everybody's start a bit smoother. Ie. I noticed that for example the volume pathes for the latest image seem to be wrong (container: /home/www-data/seeddms60x/data, but docs say to mount to /var/lib/seeddms/data).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh and should modifying the "Http Root" allow me to call the SeedDMS docker from a Nginx proxy? That'd be quite helpful to place SeedDMS to eg. /seeddms/ to have a simple rule there...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just as a hint, I started to build me a small Docker container for running SeedDMS. However, I intended it to not run standalone, but it's just a minimal "php:apache" container with some stuff added (apt-get -y install zlib1g-dev imagemagick libpng-dev poppler-utils catdoc libpq-dev id3; docker-php-ext-install gd pdo pdo_pgsql) and a bit of config:
All data is kept externally:
exec docker run \
-it \
${ARGS} \
--volume
pwd/seeddms_html:/var/www/html \--volume
pwd/seeddms_data:/var/www/html/seeddms/data \--publish 8080:80 \
seeddms
SeedDMS is extracted to the ./seeddms_html directory, it's config file modified to use the host's PostgreSQL database and all documents are also in a separate docker mount as seen above.
This should separate SeedDMS, the Apache/PHP setup, and the actual data.
There is finaly a docker image at docker hub. Search for usteinm/seeddms
Thanks a lot for this! I just started to explore this :)
Is your Dockerfile somewhere around? Or the Docker hub documentation? I'd drop a few patches to make everybody's start a bit smoother. Ie. I noticed that for example the volume pathes for the latest image seem to be wrong (container: /home/www-data/seeddms60x/data, but docs say to mount to /var/lib/seeddms/data).
Oh and should modifying the "Http Root" allow me to call the SeedDMS docker from a Nginx proxy? That'd be quite helpful to place SeedDMS to eg. /seeddms/ to have a simple rule there...
Calling it without a proxy and only the first-step minimal configuration, it "crashes" with this:
on the URL http://gw:8991/out/out.Login.php?referuri=%2Fout%2Fout.ViewFolder.php
Any hints?