How is docker workflow going?

Question

Software Deployment

Imagine a spherical web project in a vacuum.
But how are commits made?
How to develop locally with docker (i.e. code and catch changes on the fly)?
How does the web server give everything out of the container, is it necessary to somehow locally proxy the ports inside the container?
I would be grateful for any information related to docker workflow

Answer 1

DockerApp docker spherical web project:
DockerApp/ #project environment repository root
image/
web/
DockerFile
start.sh
app/
DockerFile
start.sh
db/
DockerFile
start.sh
config/
docker-compose.yml
web.conf
app.ini
db. ini
app.yml
bin/
up.sh
down.sh
show.sh
log/
app/ #submodule or external repository set to the root of the project's main codebase repository
The main development goes in app/, the changes are committed to the repository of the main codebase. The servers are started by the bin/start.sh script, which, together with config/docker-compose.yml, raises all three servers, forwarding the 80 port of the web server to the host port specified in the arguments (to 80 with sudo) and adding the host to /etc/hosts the name of the domain also specified in the arguments (i.e. bin/start.sh 80 example.com). Configs from the config directory are mounted or linked as server and application configs.
This is briefly about working on a dev-machine on a spherical project.