From 3527df959ea1a055d7bd0f0fb80f50b3cb575792 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebasti=C3=A1n=20Ram=C3=ADrez?= Date: Mon, 11 Mar 2024 20:54:22 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Add=20the=20required=20GitHub=20?= =?UTF-8?q?Actions=20secrets=20to=20docs=20(#679)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- deployment.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/deployment.md b/deployment.md index 87f55a2287..ade07a04e3 100644 --- a/deployment.md +++ b/deployment.md @@ -146,7 +146,7 @@ You can set several variables, like: ### Generate secret keys -Some environment variables in the `.env` file have a default value of `changethis`. +Some environment variables in the `.env` file have a default value of `changethis`. You have to change them with a secret key, to generate secret keys you can run the following command: @@ -244,7 +244,17 @@ You can read more about it in the official guide: [Configuring the self-hosted r On your repository, configure secrets for the environment variables you need, the same ones described above, including `SECRET_KEY`, etc. Follow the [official GitHub guide for setting repository secrets](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository). -The current Github Actions workflows expect two secrets: `DOMAIN_STAGING` and `DOMAIN_PRODUCTION`. +The current Github Actions workflows expect these secrets: + +* `DOMAIN_PRODUCTION` +* `DOMAIN_STAGING` +* `EMAILS_FROM_EMAIL` +* `FIRST_SUPERUSER` +* `FIRST_SUPERUSER_PASSWORD` +* `PGADMIN_DEFAULT_EMAIL` +* `PGADMIN_DEFAULT_PASSWORD` +* `POSTGRES_PASSWORD` +* `SECRET_KEY` ## GitHub Action Deployment Workflows