forked from coop-cloud/docs.coopcloud.tech
52 lines
960 B
Markdown
52 lines
960 B
Markdown
---
|
|
title: Packaging handbook
|
|
---
|
|
|
|
## Create a new recipe
|
|
|
|
TODO.
|
|
|
|
## Make a new release
|
|
|
|
TODO.
|
|
|
|
## Generate the recipe catalogue
|
|
|
|
TODO.
|
|
|
|
## Enable healthchecks
|
|
|
|
TODO.
|
|
|
|
## Tuning deploy configs
|
|
|
|
TODO.
|
|
|
|
## Tuning resource limits
|
|
|
|
TODO.
|
|
|
|
## Enable A+ SSL ratings
|
|
|
|
TODO.
|
|
|
|
## Thread environment variables
|
|
|
|
TODO.
|
|
|
|
## Entrypoint hacks
|
|
|
|
TODO.
|
|
|
|
### Exposing secrets
|
|
|
|
TODO.
|
|
|
|
### /bin/bash is missing?
|
|
|
|
TODO.
|
|
|
|
## Referening service names in configs?
|
|
|
|
When referencing an `app` service in a config file, you should prefix with the `STACK_NAME` to avoid namespace conflicts (because all these containers sit on the traefik overlay network). You might want to do something like this `{{ env "STACK_NAME" }}_app` (using the often obscure dark magic of the Golang templating language). You can find examples of this approach used in the [Peertube recipe](https://git.coopcloud.tech/coop-cloud/peertube/src/commit/d1b297c5a6a23a06bf97bb954104ddfd7f736568/nginx.conf.tmpl#L9).
|