From 3a92e571145813fcaf5b9023bb031408f3e7747b Mon Sep 17 00:00:00 2001 From: decentral1se Date: Tue, 14 Feb 2023 08:17:05 +0100 Subject: [PATCH] docs: improved wording & references --- docs/maintainers/handbook.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/maintainers/handbook.md b/docs/maintainers/handbook.md index b6daf45..a2ab4a5 100644 --- a/docs/maintainers/handbook.md +++ b/docs/maintainers/handbook.md @@ -551,7 +551,7 @@ An example of this is the [`selfoss`](https://git.coopcloud.tech/coop-cloud/self ## How do I set a custom entrypoint? -Ripped from the [`coop-cloud/peertube`](https://git.coopcloud.tech/coop-cloud/peertube) recipe but shortened down, here are more or the steps you need to take: +For more context, see the [`entrypoint.sh`](/maintainers/handbook/#entrypointsh) section. The following configuration example is ripped from the [`coop-cloud/peertube`](https://git.coopcloud.tech/coop-cloud/peertube) recipe but shortened down. Here are more or less the steps you need to take: Define a config: @@ -622,7 +622,7 @@ cp -ar /app/client/dist /srv/client Please note: -1. The `file_env` // `_FILE` hack is to pass secrets into the container runtime without exposing them in plaintext in the configuration. +1. The `file_env` // `_FILE` hack is to pass secrets into the container runtime without exposing them in plaintext in the configuration. See [this entry](/maintainers/handbook/#exposing-secrets) for more. 1. In order to pass execution back to the original entrypoint, it's a good idea to find the original entrypoint script and run it from your own entrypoint script. If there is none, you may want to reference the `CMD` definition or if that isn't working, try to actually specify `cmd: ...` in the `compose.yml` definition (there are other recipes which do this).