浅念
601451f22b
Overlay ~150 upstream items onto our V8.12 base, preserving trade-pro
theme, registry tests, and design docs. Re-applied our patch set
(discovery/env_for/blocks.css/type-mapping/theme_color/frontend entries,
test_theme_pro_v3 mods) — all anchors survived upstream evolution.
New platform enhancement (fixes upgrade-introduced regression):
multilingual.site_locale now honors settings_json.locale, plus
PUT /api/i18n/sites/{id}/locale — standalone English sites get
<html lang='en'> under the V8.15 locale-rewrite pipeline.
compose: adopt V8.21.3 (image 8.21.3-dev.1, /api/ready probes, MySQL/S3
env) with project name pinned to siteforge-v8-10 (data volumes).
Tests: 356 passed / 11 failed — all 11 confirmed pre-existing in
pristine V8.21.3 on this host (10 upstream Windows env + our build test
now green after locale fix). Patch registry updated in plan doc.
Co-Authored-By: Claude Code <noreply@anthropic.com>
43 lines
2.0 KiB
Bash
43 lines
2.0 KiB
Bash
# 复制为 .env 后更换密码和密钥；不要提交 .env 到版本库
|
|
SITEFORGE_PORT=8787
|
|
SITEFORGE_ADMIN_PASSWORD=REPLACE_WITH_STRONG_PASSWORD
|
|
SITEFORGE_SESSION_SECRET=REPLACE_WITH_64_RANDOM_CHARACTERS
|
|
SITEFORGE_COOKIE_SECURE=false
|
|
|
|
# 只有启用 compose.public.yaml 时才需要填写，先正确设置 DNS 记录
|
|
SITEFORGE_DOMAIN=siteforge.example.com
|
|
|
|
# Enterprise-only (compose.enterprise.yaml)
|
|
SITEFORGE_PG_USER=siteforge
|
|
SITEFORGE_PG_PASSWORD=GENERATE_STRONG_URL_SAFE_PASSWORD
|
|
SITEFORGE_PG_DB=siteforge
|
|
# Must be HTTPS and trusted deployment endpoint; never set to an arbitrary user URL
|
|
SITEFORGE_DEPLOY_STAGING_URL=
|
|
SITEFORGE_DEPLOY_STAGING_SECRET_REF=
|
|
SITEFORGE_DEPLOY_PRODUCTION_URL=
|
|
SITEFORGE_DEPLOY_PRODUCTION_SECRET_REF=
|
|
# Release agent is deployed as an isolated service on the receiving host
|
|
SITEFORGE_DEPLOY_SECRET=
|
|
|
|
# P1 task-queue capacity and safe outbound HTTP policy
|
|
SITEFORGE_MAX_PENDING_JOBS=100
|
|
SITEFORGE_MAX_PENDING_JOBS_PER_SITE=5
|
|
SITEFORGE_OUTBOUND_PORTS=80,443
|
|
|
|
# V8.5 restricted MySQL importer. Empty allowlists disable MySQL access.
|
|
# Example values, only enable an approved server + an actual SELECT-only user.
|
|
SITEFORGE_MYSQL_ALLOWED_HOSTS=
|
|
SITEFORGE_MYSQL_ALLOWED_TABLES=
|
|
# Optional CA path inside Worker. Mount certificate into Worker when using custom CA.
|
|
SITEFORGE_MYSQL_CA_FILE=
|
|
# Credential names should be secrets in Worker, not plaintext from the browser.
|
|
# SITEFORGE_MYSQL_READ_USER=<use Docker secret instead>
|
|
# SITEFORGE_MYSQL_READ_PASSWORD=<use Docker secret instead>
|
|
# Preferred remote signing secret reference (instead of plaintext _SECRET)
|
|
# SITEFORGE_DEPLOY_STAGING_SECRET_REF=env:SITEFORGE_STAGING_TOKEN
|
|
# SITEFORGE_STAGING_TOKEN=<independent random 32+ char token, delivered only to Worker>
|
|
# SITEFORGE_DEPLOY_PRODUCTION_SECRET_REF=file:siteforge_deploy_production
|
|
# Mount /run/secrets/siteforge_deploy_production in Worker using a private Compose override.
|
|
# Set SITEFORGE_DEPLOY_SECRET_REF=file:siteforge_deploy_production in the remote Agent.
|
|
# Never reuse the same token between staging and production.
|