Integrate Prisma for content; enhance SEO, i18n, and deployment workflows
Co-authored-by: dennis <dennis@konkol.net>
This commit is contained in:
@@ -34,6 +34,14 @@ N8N_API_KEY=your-n8n-api-key
|
||||
# JWT_SECRET=your-jwt-secret
|
||||
# ENCRYPTION_KEY=your-encryption-key
|
||||
ADMIN_BASIC_AUTH=admin:your_secure_password_here
|
||||
ADMIN_SESSION_SECRET=change_me_to_a_long_random_string_at_least_32_chars
|
||||
|
||||
# Prisma migrations at container startup
|
||||
# - default: migrations are executed (`prisma migrate deploy`)
|
||||
# - set to true ONCE if you already have an existing DB that was created before migrations existed
|
||||
PRISMA_AUTO_BASELINE=false
|
||||
# emergency switch (not recommended for normal operation)
|
||||
# SKIP_PRISMA_MIGRATE=true
|
||||
|
||||
# Monitoring (optional)
|
||||
# SENTRY_DSN=your-sentry-dsn
|
||||
|
||||
Reference in New Issue
Block a user