Add Docker Compose profiles for dev and prod server setups (#198)
Since we are moving towards always running against Postgres, just
using `lnt runserver` without any Postgres server will eventually
stop being supported. To avoid creating a barrier for running local
instances, I want to make it easier to run a "real" server locally
backed by Postgres.
To do that, the easiest way is to simplify the Docker Compose setup
so that a full service can be brought up for local development in a
single command. This is achieved using profiles:
- Default (no profile): starts db + webserver, built from source, bound to
localhost:8000. Suitable for local development:
docker compose -f docker/compose.yaml --env-file docker/dev.env up
- prod profile: adds Nginx reverse proxy on port 80. The production
deployment uses docker/compose.prod.yaml as an override to pull the
pre-built LNT image from ghcr.io and bind volumes to the host
filesystem, like it used to.LNT is an infrastructure for performance testing. The software itself consists of two main parts, a web application for accessing and visualizing performance data, and command line utilities to allow users to generate and submit test results to the server.
The package was originally written for use in testing LLVM compiler technologies, but is designed to be usable for the performance testing of any software.
The official LNT documentation is available online at: https://llvm.org/docs/lnt
The LNT source is available in the llvm-lnt repository: https://github.com/llvm/llvm-lnt
To get started, please look at the Developer Guide in the official documentation.