@@ -144,6 +144,8 @@ Essentially `docker-compose.yaml` the same information as in the Makefile, but e
The service can be started with `docker-compose up` (or with `docker-compose up --build` to build the image itself). If you make a change to the service, you can run `docker-compose down` and `docker-compose up --build` to bring down, rebuild and bring up the service again. If you are merely intending to restart the service, you can run `docker-compose stop` and `docker-compose start`.
The [docker compose specification](https://github.com/compose-spec/compose-spec/blob/master/spec.md) gives full details about what you can say in a `docker-compose.yaml` file. There is also a [Getting Started](https://docs.docker.com/compose/gettingstarted/) guide and a [full reference of the Docker Compose CLI](https://docs.docker.com/compose/reference/).
## Even further steps
> The above is already much more easier than running by hand all the commands in the makefile, or creating the makefile from scratch. However, during development, we will frequently find that the source code within the container has a bug and we need to make a tiny change and restart the service. This quickly becomes a pain. We can avoid this if we can figure out a way to change source code within a running container. Move to the branch `hotsource' to find out how.
