Checking the installation and logs

The server's half

verify-install.sh from the delivery bundle checks the server's half of the installation: the files and .env, the containers, the application, the public address, disk space, memory and the clock. It only reads; nothing is started, stopped or changed, and no secret from .env is printed. Run it in the installation directory:

cd /data/goproject
sh verify-install.sh
sh verify-install.sh https://goproject.example.com

Without an address it checks the one in SITE_URL. Every line says OK, WARN or FAIL, with what to do under the ones that are not OK. The exit code is 0 when everything is in order, 1 when something needs a look and 2 when something has to be fixed.

The application's half

Migrations, the two clocks, mail, licence, administrators and live updates in the browser are checked in Administration > System information > Installation check, with a report you can download and hand on.

Logs

Follow the application's log:

docker compose logs -f app

The database's log is docker compose logs -f db. Both are kept by Docker with a size limit, so old lines go by themselves.