From 6fd56334e2d19c7ead0c4dc000cc0113110c5fda Mon Sep 17 00:00:00 2001
From: Paul Bienkowski <pb@opatut.de>
Date: Mon, 20 Dec 2021 11:33:17 +0100
Subject: [PATCH] Explain to use the portal service, instead of api, in
 production

---
 deployment/README.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/deployment/README.md b/deployment/README.md
index 4a464b8..656a523 100644
--- a/deployment/README.md
+++ b/deployment/README.md
@@ -79,8 +79,16 @@ sure to configure:
 ### Prepare database
 
 Follow the procedure outlined in [README.md](../README.md) under "Prepare
-database".
+database". Whenever the docker-compose service `api` is referenced, replace it
+with `portal`, which contains the same python code as the development `api`
+service, but also the frontend. For example:
 
+```bash
+# development
+docker-compose run --rm api tools/prepare_sql_tiles.py
+# production
+docker-compose run --rm portal tools/prepare_sql_tiles.py
+```
 
 ### Import OpenStreetMap data