From 026cc29e1f1348ca833ba5c7e520b71c819aa6cc Mon Sep 17 00:00:00 2001 From: Laurens Nienhaus <94158+laurens@users.noreply.github.com> Date: Sat, 27 Jul 2024 11:11:05 +0200 Subject: [PATCH] docs: unify CRON_SECRET descriptions (#2915) Co-authored-by: laurens --- .env.example | 2 +- docker/docker-compose.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.env.example b/.env.example index d994f929b7..1b27a3a771 100644 --- a/.env.example +++ b/.env.example @@ -34,7 +34,7 @@ DATABASE_URL='postgresql://postgres:postgres@localhost:5432/formbricks?schema=pu # You can use: `openssl rand -hex 32` to generate a secure one NEXTAUTH_SECRET=RANDOM_STRING -# Cron Secret (mandatory) +# API Secret for running cron jobs. (mandatory) # You can use: `openssl rand -hex 32` to generate a secure one CRON_SECRET=RANDOM_STRING diff --git a/docker/docker-compose.yml b/docker/docker-compose.yml index a86776318a..edbcb82066 100644 --- a/docker/docker-compose.yml +++ b/docker/docker-compose.yml @@ -22,7 +22,7 @@ x-environment: &environment # You can use: $(openssl rand -hex 32) to generate one ENCRYPTION_KEY: - # Set the below to use it instead of API Key for the API & use as an auth for cronjobs + # API Secret for running cron jobs. # You can use: $(openssl rand -hex 32) to generate a secure one CRON_SECRET: