devilbox/docs/Run.md

Devilbox Documentation

Overview | Quickstart | Install | Update | Configure | Run | Usage | Backups | Examples | Technical | Hacking | FAQ

---

Run

1. Start the devilbox
2. Foreground Start
3. Background Start
4. Selective Start
5. Stop the devilbox
6. Foreground Stop
7. Background Stop
8. Attach/Detach during run-time
9. Attach during run-time
10. Detach during run-time
11. Docker logs
12. All logs
13. Specific logs
14. Tail logs

---

1. Start the devilbox

Starting and stopping containers is done via docker-compose. If you have never worked with it before, have a look at their documentation for an overview, up and stop commands.

By starting up the devilbox all attached containers will send their stdout and stderr to docker logs (foreground or background), you can increase/decrease the containers startup verbosity by configuring the .env file. See Configure for how to change that behavior.

1.1 Foreground Start

The normal start will bring up all container defined in docker-compose.yml and will stay in forground making it possible to stop them via Ctrl+c.

$ docker-compose up

1.2 Background Start

Instead of having the docker-compose run stay in foreground, you can also send it to the background by adding -d as an argument. The following will bring up all container and send docker-compose to background.

$ docker-compose up -d

1.3 Selective Start

There is no need to always bring up all container, if you just need a few at the moment. In order to do so, simply specify the container by name that you actually need.

1.3.1 Starting httpd, php, bind and mysql

# Foreground
$ docker-compose up httpd php bind mysql

# Background
$ docker-compose up -d httpd php bind mysql

Start Note: httpd, php and bind are base container that will always be started if specified or not. (Defined by depends_on in docker-compose.yml). So the above could also be achieved by simply specifying mysql only.

# Foreground
$ docker-compose up mysql

# Background
$ docker-compose up -d mysql

Log Note: When you do not specify httpd, php and bind in foreground start, their docker-logs will not be shown and you will have to explicitly use docker-compose logs to view their stdout/stderr output. Refer to the Log section below.

1.3.2 Starting httpd, php, bind, pgsql and redis

# Foreground
$ docker-compose up httpd php bind pgsql redis

# Background
$ docker-compose up -d httpd php bind pgsql redis

Start Note: httpd, php and bind are base container that will always be started if specified or not. (Defined by depends_on in docker-compose.yml). So the above could also be achieved by simply specifying pgsql and redis only.

# Foreground
$ docker-compose up pgsql redis

# Background
$ docker-compose up -d pgsql redis

Log Note: When you do not specify httpd, php and bind in foreground start, their docker-logs will not be shown and you will have to explicitly use docker-compose logs to view their stdout/stderr output. Refer to the Log section below.

2. Stop the devilbox

2.1 Foreground stop

If you started up docker compose in foreground mode (without -d), you can hit ctrl+c to gracefull stop or twice ctrl+c to kill the running containers.

Note: Automatically started containers that were not specified (such as http or php) will have to be stopped manually via docker-compose down afterwards.

2.2 Background stop

If you started up docker compose in background mode (with -d), go back to the devilbox directory (where the docker-compose.yml file resides and type docker-compose down to gracefully stop or docker-compose kill to kill them immediately.

# Gracefully shutdown everything
$ docker-compose down

# Kill everything immediately
$ docker-compose kill

Best pracice would be to start the container in the background (with -d) and use docker compose down to gracefully stop all of them.

3. Attach/Detach during run-time

3.1 Attach during run-time

You can also add/attach containers during runtime if you need them. You might have started httpd, php, bind and mysql and decided that you will also require redis. So go ahead and add redis to the running container stack.

# Foreground
$ docker-compose up redis

# Background
$ docker-compose up -d redis

It is recommended to always use background starts, this way you can intially start your desired stack and re-use the current terminal window to start or stop other services.

3.2 Detach during run-time

You can also stop specific containers during runtime if they are not needed anymore. You might have started httpd, php, bind, mysql and redis and decided that redis was not needed. So go ahead and remove redis from the running container stack.

$ docker-compose stop redis

4. Docker Logs

Services started in background mode (-d) or those that were started as dependencies (http and php) will always only log to docker logs and not to stdout/stderr.

4.1 All logs

In order to view logs of all started containers type:

$ docker-compose logs

4.2 Specific logs

In order to view logs of a specific container, name it explicitly:

$ docker-compose logs redis

4.3 Tail logs

There is also a version similar to tail -f to keep logs updated all the time.

$ docker-compose logs -f