Running Ecodms in a docker environment, using docker compose
This docker-compose file creates a container for ecodms 18.09 with persistent data store. You can either take the storage layout, or choose your own folders by editing the docker-compose file.
Ecodms document and database data will be stored in a subfolder called data/ecodmsData relative to path where the docker-compose file is stored.
The same is true for the scaninput folder, which will be stored in a subfolder called data/scaninput
For example, if the docker-compose file is places in /opt/ecodms, then the data folder will be /opt/ecodms/data/ecodmsData and the scan folder will be /opt/ecodms/data/scaninput
Ecodms has the capability to easily create backups and to be easily restored. For this there exist two folders, which in this case are placed under /data/ecodms-backup and /data/ecodms-restore
If you want to backup your ecodms container data, just create an empty file called "create" in the backup folder, shortly after the backup will be created as a zip file and then the "create" file will be removed
For example: touch /data/ecodms-backup/create
If you want to restore a backup then place one of the *.zip files that you have created in the folder /data/ecodms-restore and remname it to restore.zip.
Then restart the container with docker-compose down && docker-compose up -d and the restore will be performed
BUT BE AWARE, this will overwrite ALL DATA in the ecodms container with the data from restore.zip
Appliaction ports can also be adjusted to your likings by editing the ports: part in the docker-compose file
- Port 17001 which is mapped to 17001 is the connection port for the ecodms Client software
- Port 8080 which is mapped to 17004 is the web application connection port for the ecodms Web Client (this must be activated first in the application to be used
- Port 8180 which is mapped to 17005 is the ecodms API connection port for API calls
Note: By default connections are not encrypted.
If you want an encrypted connection to your cloud ecodms, you have to use some kind of VPN tunnel, for example Softether, OpenVPN, IPsec, etc., you could also use an SSL encrypted reverse proxy, as mentioned below to make a secure HTTPS connection to the ecodms Web Client
If you would like to run ecodms Webservice on your own server, e.g. in the cloud, I have attached a nginx reverse proxy configuration file, which you could edit to your likings and then place under /etc/nginx/sites-available.
Then you can link it to /etc/nginx/sites-enabled whenever you want to activate it.
For example with this command: ln -s /etc/nginx/sites-available/ecodms-reverse-proxy.conf /etc/nginx/sites-enabled/ecodms
Nginx configuration can be tested via nginx -t
To make this work, you have to make sure that you have your own webserver certificates in place, maybe Let's Encrypt and you have to create the DH paramater file for nginx if it not already exists, instructions are in the comments of the file ecodms-reverse-proxy.conf