From 7a253e0f0cac651180cc547c3ebe84412ffccb3e Mon Sep 17 00:00:00 2001
From: Codex <codex@example.com>
Date: Wed, 12 Nov 2025 10:17:13 -0600
Subject: [PATCH] Use printenv when writing runtime env

---
 CloudronManifest.json | 2 +-
 start.sh              | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/CloudronManifest.json b/CloudronManifest.json
index 0e2b967..db047ad 100644
--- a/CloudronManifest.json
+++ b/CloudronManifest.json
@@ -5,7 +5,7 @@
   "description": "Next-gen knowledge base that blends docs, whiteboards, and databases for self-hosted teams.",
   "website": "https://affine.pro",
   "contactEmail": "support@affine.pro",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "changelog": "Initial Cloudron packaging",
   "manifestVersion": 2,
   "minBoxVersion": "7.0.0",
diff --git a/start.sh b/start.sh
index 2a953ba..1f4b152 100644
--- a/start.sh
+++ b/start.sh
@@ -147,7 +147,7 @@ write_runtime_env() {
   )
   local var value
   for var in "${vars[@]}"; do
-    value="${!var-}"
+    value=$(printenv "$var" 2>/dev/null || true)
     if [ -n "$value" ]; then
       printf '%s=%q\n' "$var" "$value" >> "$ENV_EXPORT_FILE"
     fi