Support for runtime ENV vars

[thunder-007]

Goals

1. Having the env vars hard code into build is not the right way.
2. I don't want to build every time I change env vars
3. It's more secured to have env vars on the runtime only on the process.

Background

I'm trying to pass the env vars to docker container and it's not working

# Use a minimal Node.js image as the base
FROM node:18-alpine AS base

WORKDIR /app

# Install dependencies only when needed
FROM base AS deps

RUN apk add --no-cache libc6-compat
# Install pnpm
RUN npm install -g pnpm

# Copy package manager files and install dependencies
COPY package.json package-lock.json* pnpm-lock.yaml* .npmrc* ./

RUN pnpm install --frozen-lockfile

# Build the application in a separate layer
FROM base AS build

COPY --from=deps /app/node_modules ./node_modules
COPY . .

RUN npm install -g pnpm

RUN pnpm run build

# Create a separate serve layer for better caching
FROM base AS serve

COPY sshd_config /etc/ssh/
COPY ./start.sh ./

RUN apk update \
    && apk upgrade \
    && apk add --no-cache openssh \
    && echo "root:Docker!" | chpasswd \
    && cd /etc/ssh/ \
    && ssh-keygen -A

WORKDIR /app

ENV NODE_ENV=production
ENV HOSTNAME="0.0.0.0"
ENV PORT=3000


RUN chmod +x start.sh

COPY --from=build --chown=nextjs:nodejs /app/public ./public
COPY --from=build --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=build --chown=nextjs:nodejs /app/.next/static ./.next/static

EXPOSE 80/tcp 3000 2222

ENTRYPOINT ["./start.sh"]

Startup script

#!/bin/sh
/usr/sbin/sshd

node server.js

Proposal

There should be a inbuilt support for next to accept runtime environment variables.