-
Notifications
You must be signed in to change notification settings - Fork 1
01 Installation
For production usage a reverse proxy is absolutely necessary. If you are only using it for testing purposes or on local network you can do without. More details on this later in the guide.
Create a directory for config files and persistent data
mkdir tierrating
cd tierrating
wget https://raw.githubusercontent.com/RatzzFatzz/tierrating/refs/heads/dev/docker-compose.example.yaml -O docker-compose.yml
wget https://raw.githubusercontent.com/RatzzFatzz/tierrating/refs/heads/dev/.env.example -O .envMake sure the update security related environment variables:
- DB_PASSWORD
- SECRET_KEY
After updating all relevant parameters run to start the services:
docker compose up -dTierrating consists of an api and a webapp. We use the reverse proxy to rewrite the url and provide everything under one domain.
Ports need to be updated according to the configuration made previously.
tierrating.example.de {
handle /api* {
reverse_proxy localhost:8080
}
handle {
reverse_proxy localhost:3000
}
}
If you are using tierrating in a development or testing environment and are not exposing it to the internet you don't need to configure a reverse proxy.
Make sure to update the API_URL environment variable for the webapp to know the location of the api. It will then use NextJS rewrites to reach the api, without needing above steps.
I don't recommend this setup for production use.