update from sparkleup

work/gitea-2.md

@@ -49,6 +49,26 @@ Given that all of the information stored in this directory is important to us, w
 
 ### Using a new installation of Gitea
 
+If you are starting with a brand new installation of Gitea, you can specify where all of your information is stored during the configuration process. For example, if you are setting Gitea up using Docker Compose, you can map the volumes to your attached volume.
+
+Open up the `docker-compose.yml` file with your preferred text editor. The following example uses `nano`. Search for the `volumes` entry in the compose file and modify the mapping on the left side of the `:` to point to appropriate locations on your Linux volume for the Gitea data directory:
+
+```yaml
+...
+
+    volumes:
+      - <^>/media/gitea<^>:/data
+      - /home/git/.ssh/:/data/git/.ssh
+      - /etc/timezone:/etc/timezone:ro
+      - /etc/localtime:/etc/localtime:ro
+
+...
+```
+
+<$>[warning]
+**Warning:** SSH servers look for the `.ssh` directory, which contains all of the SSH keys that Gitea will use, in the home directory of the Git user (`git`, in this case), so it is not advised to move the mount for this Docker volume. In order to have this location backed up on your Linux volume, it would be best to use another solution such as a `cron` job to back up the directory. For more information on using `cron` to manage scheduled tasks, see [this tutorial](https://www.digitalocean.com/community/tutorials/how-to-use-cron-to-automate-tasks-ubuntu-1804).
+<$>
+
 ### Using an existing installation of Gitea
 
 ## Step 3 — Creating Snapshots of Volumes (optional)