Scott.Idem/OSIT-AE-App-Svelte
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

DevOps: add svelte-kit sync step to Dockerfile before build

Browse Source 
Fixes a build warning about missing .svelte-kit/tsconfig.json that
appears when building inside Docker. Running npx svelte-kit sync
pre-generates the required SvelteKit scaffolding before the main
build step.

Also update README title to reflect Svelte v5 and trim a trailing
whitespace in the environment handling section.
This commit is contained in:
Scott Idem
2026-03-10 14:20:40 -04:00
parent 18462249b3
commit 2c0eba4130
2 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Dockerfile
View File

@@ -16,6 +16,10 @@ COPY . .
ARG BUILD_MODE=staging ARG BUILD_MODE=staging
ENV NODE_ENV=production ENV NODE_ENV=production
# Sync the SvelteKit project to generate ./.svelte-kit/tsconfig.json
# and other required files, which avoids the build warning.
RUN npx svelte-kit sync
# Perform the build based on the BUILD_MODE argument. # Perform the build based on the BUILD_MODE argument.
# This runs the existing scripts in package.json, which already # This runs the existing scripts in package.json, which already
# handle copying the correct .env file to .env.production for Vite. # handle copying the correct .env file to .env.production for Vite.

4
README.md
View File

@@ -1,4 +1,4 @@
# One Sky IT's Aether App - SvelteKit v2 # One Sky IT's Aether App - SvelteKit v2 with Svelte v5
This uses SvelteKit version 2.x with Svelte version 5.x, DexieJS 4.x, TailwindCSS 4.1, and Skeleton. This uses SvelteKit version 2.x with Svelte version 5.x, DexieJS 4.x, TailwindCSS 4.1, and Skeleton.
@@ -145,7 +145,7 @@ npm run deploy:prod
- **Unified Orchestration**: All services (API, UI, Redis) are managed via `~/OSIT_dev/aether_container_env/docker-compose.yml`. - **Unified Orchestration**: All services (API, UI, Redis) are managed via `~/OSIT_dev/aether_container_env/docker-compose.yml`.
- **Dockerfile**: Uses a multi-stage build. Stage 1 (builder) installs dependencies and builds the app using the `BUILD_MODE` argument passed from Docker Compose. Stage 2 (runtime) creates the final lightweight image. - **Dockerfile**: Uses a multi-stage build. Stage 1 (builder) installs dependencies and builds the app using the `BUILD_MODE` argument passed from Docker Compose. Stage 2 (runtime) creates the final lightweight image.
- **Environment Handling**: - **Environment Handling**:
- `PUBLIC_` variables are baked into the image during the build step. - `PUBLIC_` variables are baked into the image during the build step.
- Private runtime variables are passed via the orchestration's `.env` file. - Private runtime variables are passed via the orchestration's `.env` file.
- **Networking**: The frontend communicates with the backend via the high-speed internal Docker network (`http://ae_api:5005`). - **Networking**: The frontend communicates with the backend via the high-speed internal Docker network (`http://ae_api:5005`).