Here are the 2 basic goals and potential solutions,
Quick Local setup:
Setup env file, run docker-compose up and visit http://site-from-env-file.localhost
single docker-compose file is required with all redis, mariadb, frappe/erpnext services and port 80 published on host machine
Someone I interacted with on issue used it on LAN/WAN setup with self hosted internal DNS server. e.g. http://site-from-env-file.local-machine-01 was accessible within from LAN.
local setup is required for local api or ui development that needs to connect to erpnext server.
Quick production setup:
Setup env file, run docker-compose up and visit http://site-from-env-file.com
single docker-compose file is required with all redis, mariadb, frappe/erpnext services and some way to manage Letsencrypt.
Problem with current production setup on docker:
- VERSION is not locked. It’s locked to either major version or edge.
- VERSION can be separated into FRAPPE_VERSION and ERPNEXT_VERSION to be specific.
Way to achieve new site creation on first run:
docker-compose can have one run-once service to execute the new command to create a site.
It will anyway fail on additional runs as it will try to re-create same site again.