fix: Use npm install instead of npm ci in production stage
- Changed 'npm ci --production' to 'npm install --production' - More forgiving with cached package files in CI/CD - Matches working pattern from other deployments - Fixes Easypanel build cache issues
This commit is contained in:
@@ -19,11 +19,11 @@ FROM node:20-alpine
|
||||
|
||||
WORKDIR /app
|
||||
|
||||
# Install SQLite runtime and serve
|
||||
# Install SQLite runtime
|
||||
RUN apk add --no-cache sqlite-libs
|
||||
|
||||
COPY package*.json ./
|
||||
RUN npm ci --production
|
||||
RUN npm install --production
|
||||
|
||||
COPY --from=builder /app/dist ./dist
|
||||
COPY --from=builder /app/public ./public
|
||||
@@ -38,6 +38,7 @@ HEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \
|
||||
|
||||
ENV NODE_ENV=production
|
||||
ENV ASTRO_DB_REMOTE_URL=file:/app/data/consent.db
|
||||
ENV HOST=0.0.0.0
|
||||
ENV PORT=80
|
||||
|
||||
# Use serve to host static files on port 80
|
||||
|
||||
Reference in New Issue
Block a user