simon/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Pull Requests Activity

Minor tweaks to maintainers tutorial

Browse Source
This commit is contained in:
3wc
2023-01-08 17:13:11 -08:00
parent 765987d423
commit f0fcef3d18
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/maintainers/tutorial.md
View File

@ -21,7 +21,7 @@ The idea scenario is when the upstream project provides both the packaged image
- **Inspired**: Upstream image, someone else's compose file
- **On fire**: Upstream image, upstream compose file
### Writing the `compose.yml`
### Writing / adapting the `compose.yml`
Let's take a practical example, [Matomo web analytics](https://matomo.org/). We'll be making a Docker "swarm-mode" `compose.yml` file.
@ -66,8 +66,8 @@ abra app new matomo --secrets \
--server swarm.example.com
```
Depending on whether you defined any extra environment variables, we didn't so
far, in this example, you might want to run `abra app config swarm.example.com`
Depending on whether you defined any extra environment variables -- we didn't so
far, in this example -- you might want to run `abra app config swarm.example.com`
to check the configuration.
Otherwise, or once you've done that, go ahead and deploy the app:
@ -80,4 +80,4 @@ Then, open the `DOMAIN` you configured (you might need to wait a while for Traef
### Finishing up
You've probably got more questions, check out the [maintainers handbook](/maintainers/handbook)!
You've probably got more questions, check out the [packaging handbook](/maintainers/handbook)!