feat: add GIT_TOKEN and PG_CONNECTION_STRING to environment configuration

- Updated the .env.template to include GIT_TOKEN for remote repository authentication.
- Modified the Dockerfile to accept GIT_TOKEN and PG_CONNECTION_STRING as build arguments, enhancing the configuration for deployment.

Signed-off-by: Innei <tukon479@gmail.com>
This commit is contained in:
Innei
2025-06-28 14:19:42 +08:00
parent a4eb754243
commit 1a546bd357
2 changed files with 3 additions and 0 deletions

View File

@@ -2,3 +2,4 @@ S3_ACCESS_KEY_ID=
S3_SECRET_ACCESS_KEY= S3_SECRET_ACCESS_KEY=
PG_CONNECTION_STRING= PG_CONNECTION_STRING=
GIT_TOKEN=

View File

@@ -22,6 +22,8 @@ RUN pnpm install --frozen-lockfile
ARG S3_ACCESS_KEY_ID ARG S3_ACCESS_KEY_ID
ARG S3_SECRET_ACCESS_KEY ARG S3_SECRET_ACCESS_KEY
ARG GIT_TOKEN
ARG PG_CONNECTION_STRING
# Build the app. # Build the app.
# The build script in the ssr package.json handles building the web app first. # The build script in the ssr package.json handles building the web app first.
RUN pnpm --filter=@afilmory/ssr build RUN pnpm --filter=@afilmory/ssr build