With a docker-compose.yml file, the development environment could be set up in a single command. However, this would be a different environment than the setup explained in the README because it would build the frontend and backend Dockerfiles, which use production settings. The Caddyfile would be in use and the site would have the option to log into the admin section, which is not usually an option in development.
I'm not sure if this environment would be useful for development, but it does make sure that the Dockerfiles actually build. We also had a problem in production with 404 errors not being redirected to our 404 page, which we didn't detect in the development environment because the Caddyfile isn't used in the development environment.
With a docker-compose.yml file, the development environment could be set up in a single command. However, this would be a different environment than the setup explained in the README because it would build the frontend and backend Dockerfiles, which use production settings. The Caddyfile would be in use and the site would have the option to log into the admin section, which is not usually an option in development.
I'm not sure if this environment would be useful for development, but it does make sure that the Dockerfiles actually build. We also had a problem in production with 404 errors not being redirected to our 404 page, which we didn't detect in the development environment because the Caddyfile isn't used in the development environment.