Fix production deploy env path and homepage routing

- pass NEXT_PUBLIC_CARPLACE_URL into the production Docker build
- keep NEXT_PUBLIC_STOREFRONT_URL as a fallback for existing secrets
- run the production deploy script after building the image
- support raw or base64 production env secrets during deploy
- copy the production env file into the remote build context
- include homepage in production deploy, pull, and health checks

.gitea/workflows/build-and-deploy.yml

@@ -323,7 +323,7 @@ jobs:
           REGISTRY_PASSWORD_B64="$(printf '%s' "$REGISTRY_PASSWORD" | base64 | tr -d '\n')"
           ssh $SSH_OPTIONS "${{ secrets.VPS_USER }}@$VPS_HOST" "
             set -e
-            mkdir -p '$DEPLOY_ROOT'
+            mkdir -p '$DEPLOY_ROOT' '$REMOTE_BUILD_DIR'
             if [ -n '$ENV_DOCKER_PRODUCTION_B64_CLEAN' ]; then
               printf '%s' '$ENV_DOCKER_PRODUCTION_B64_CLEAN' | base64 -d > '$DEPLOY_ROOT/.env.docker.production'
               chmod 600 '$DEPLOY_ROOT/.env.docker.production'
@@ -336,6 +336,8 @@ jobs:
             else
               echo 'Using existing $DEPLOY_ROOT/.env.docker.production on the VPS'
             fi
+            cp '$DEPLOY_ROOT/.env.docker.production' '$REMOTE_BUILD_DIR/.env.docker.production'
+            chmod 600 '$REMOTE_BUILD_DIR/.env.docker.production'
             cd '$REMOTE_BUILD_DIR'
             export APP_IMAGE='$DEPLOY_REGISTRY_HOST/$IMAGE_REPOSITORY'
             export IMAGE_TAG='$IMAGE_TAG'