I have a Docker Compose file with close to 6 services each having its own .env
file. To launch the application, some of these .env
files might have to be edited. Once edited, the application is launched with docker compose up -d
.
The user base who is expected to use this application is not very tech savvy. I wonder, if there was an installer kind of approach. The expectation is the .env
files are edited via the installer (think a Electron app, etc.) and a Deploy
or a Submit
button click launches the docker compose up -d
command.
Thoughts?