From adbc26cdc365c04d42c60f4b69d61583dc97bade Mon Sep 17 00:00:00 2001
From: mrkvon <mrkvon@protonmail.com>
Date: Thu, 15 Jun 2023 18:06:45 +0200
Subject: [PATCH] Document detailed steps to deploy frontend to dev server

---
 docs/deployment.md | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/docs/deployment.md b/docs/deployment.md
index 406c7c7..880a336 100644
--- a/docs/deployment.md
+++ b/docs/deployment.md
@@ -6,6 +6,27 @@ Make a commit to https://github.com/hnuti-brontosaurus/bis which includes `#depl
 
 So, e.g. you can update its frontend submodule, and make a commit with message `chore: update frontend #deploy`. In any case, please use commit messages consistent with current backend commit style.
 
+### Detailed steps to deploy new frontend version to development server
+
+1. have github repository [hnuti-brontosaurus/bis-frontend](https://github.com/hnuti-brontosaurus/bis-frontend/) updated with your changes
+1. clone [hnuti-brontosaurus/bis](https://github.com/hnuti-brontosaurus/bis) onto your computer, including submodules (or update it to latest version with `git pull`)
+   ```bash
+   git clone --recurse-submodules https://github.com/hnuti-brontosaurus/bis.git
+   ```
+1. go to `frontend` folder
+   `cd bis/frontend`
+1. update the frontend submodule
+   ```bash
+   git pull
+   ```
+1. go back to `bis`, commit the changes, and push them to remote master
+   ```bash
+   cd ..
+   git add frontend
+   git commit -m "chore: update frontend #deploy"
+   git push
+   ```
+
 ## Deployment to production server
 
 When commit in https://github.com/hnuti-brontosaurus/bis is tagged with tag `v*.*.*`, a production build gets created. Then an administrator has to confirm the deployment.