Add separate production, testserver, and demo deployments

remote/setup/.env.example

@@ -1,7 +1,7 @@
-# Copy this file to .env next to provision-server.sh and restrict it to the
-# administrator. The file is sourced as Bash configuration and must be trusted.
-#   cp .env.example .env
-#   chmod 600 .env
+# Copy this template to .env, .env.testserver, and .env.demo as needed. Keep
+# separate database credentials and URLs in every file. The files are sourced
+# as Bash configuration and must be trusted and restricted to the administrator.
+# `make config/init` creates all three with mode 0600.
 
 # Server provisioning ---------------------------------------------------------
 
@@ -70,6 +70,13 @@ GARDOMATIC_RATE_LIMIT_BURST='40'
 # https://garden.example.com,https://admin.example.com
 GARDOMATIC_CORS_TRUSTED_ORIGINS=''
 
+# Destructive demo reset. Leave false on every non-demo database. When true,
+# deployments require /etc/gardomatic/demo-password and enable the nightly timer.
+GARDOMATIC_DEMO_RESET_ENABLED='false'
+# Required when the demo reset is enabled. The API protects this shared account's
+# profile, email address, password and sessions from changes by visitors.
+GARDOMATIC_DEMO_ACCOUNT_EMAIL=''
+
 # Delivery mode. Allowed exactly: file or smtp. Production normally uses smtp.
 GARDOMATIC_SMTP_MODE='smtp'
 # Required in smtp mode: resolvable SMTP hostname and TCP port.