nav indents

docs/maintainers/tutorial.md

@@ -69,7 +69,7 @@ abra app mygreatapp deploy
 
 Then, open the `DOMAIN` you configured (you might need to wait a while for Traefik to generate SSL certificates) to finish the set-up. Luckily, this container is (mostly) configurable via environment variables -- if we want to auto-generate the configuration we can use a `config` and / or a custom `entrypoint` (see [`coop-cloud/mediawiki`](https://git.autonomic.zone/coop-cloud/mediawiki) for examples of both).
 
-## How recipes are versioned
+### How recipes are versioned
 
 > We are still working on stabilising this workflow
 
@@ -89,7 +89,7 @@ The commands uses for dealing with this logic in `abra` are:
 - `abra recipe tag`: publish a git tag for the recipe repo
 - `abra recipe sync`: upgrade the deploy labels to match the new recipe version
 
-## How to publish a new recipe version
+### How to publish a new recipe version
 
 !!! warning
 
@@ -101,7 +101,7 @@ The commands uses for dealing with this logic in `abra` are:
 - `abra recipe sync keycloak "1.0.0+13.0.1"`
 - `abra recipe release -c --cm "chore: first release" -t "first release" --push`
 
-## Style guide
+### Style guide
 
 - Please don't use `&image` YAML repeat anchors on the `image: ...` key because our `recipe release` logic does not handle it (see [#172](https://git.autonomic.zone/coop-cloud/abra/issues/172))
 
@@ -117,7 +117,7 @@ A recipe is a git repository that contains instructions for creating stacks that
 - [other files](#other-files)
 
 
-## compose.yml
+### compose.yml
 
 this is a [compose specification](https://compose-spec.io/) compliant file that contains a list of:
 
@@ -130,26 +130,26 @@ this is a [compose specification](https://compose-spec.io/) compliant file that
 that describe what is needed to run a stack. Whenever you deploy an app, abra reads this file to cook the stack.
 
 
-## .env.sample
+### .env.sample
 
 this file is a skeleton for environmental variables that should be adjusted by the user. Examples include: domain or php extention list. Whenever you create a new app with `abra app new` this file gets copied to the ~/.abra/servers/server-domain/app-name.env and when you run `abra app config` you're editing this file.
 
 
-## abra.sh
+### abra.sh
 
 `abra.sh` provides shell functions for running non-standard deploy, restore, rollback, backup and upgrade. This is only needed for some packages (such as nextcloud or wordpress)
 
 
-## entrypoint.sh
+### entrypoint.sh
 
 after docker creates the filesystem and copies files into a new container it runs what's called an entrypoint. This is usually a shell script that exports some variables and runs the application. Sometimes the vendor entrypoint doesn't do everything that we need it to do. In that case you can write your own entrypoint, do whatever you need to do and then run the vendor entrypoint. For a simple example check [entrypoint.sh for croc](https://git.coopcloud.tech/coop-cloud/croc/src/commit/2f06e8aac52a3850d527434a26de0a242bea0c79/entrypoint.sh). In this case, croc needs the password to be exported as an environmental variable called `CROC_PASS`, and that is exactly what the entrypoint does before running vendor entrypoint. If you write your own entrypoint, it needs to be specified in the `config` section of compose.yml.
 
 
-## other compose files
+### other compose files
 
 i.e. compose.smtp.yml. These are used to provide non-essential functionality such as (registration) e-mails or single sign on.
 
 
-## other files
+### other files
 
 if you look at compose.yml (or compose.\*.yml) and see a `configs` section, that means this compose file is putting files in the container. This might be used for changing default (vendor) configuration, such as this [fpm-tune.ini file](https://git.coopcloud.tech/coop-cloud/nextcloud/src/commit/28425b6138603067021757de28c639ad464e9cf8/fpm-tune.ini) used to adjust php-fpm.