Files
neuron-web/Dockerfile
T
Will Anderson 269eed41aa feat: El-native landing replaces the Next.js site, Dockerfile + build.sh
Hand-cuts the marketing surface from Next.js to a native El HTTP server.
The El landing reads the pre-rendered index.html (output of the existing
component pipeline at src/index.html) and serves it directly. ~150
lines of El at server.el; 130 KB binary; no Node, no build step at
serve-time, no runtime JS for the marketing pages.

What's here:

  - server.el: dispatcher with /, /health, /api/founding-count, /assets/*,
    /brand/*, 404 JSON for everything else. Routes go through fs_read
    against LANDING_ROOT (default /srv/landing in the container, ./src
    locally).

  - Dockerfile: two-stage build for linux/amd64 (Cloud Run target).
    Stage 1 — debian:bookworm-slim with build-essential + libcurl-dev,
    compiles the binary against el_runtime.c. Stage 2 — slim runtime
    image with libcurl4 + ca-certificates, drops the binary at
    /usr/local/bin/landing, copies src/index.html and src/assets/ into
    /srv/landing/. Uses -rdynamic so the runtime's dlsym(RTLD_DEFAULT,
    handler_name) can find handle_request inside the executable on
    glibc — macOS exposes executable symbols by default, Linux does
    not. Links -lcurl -lpthread -ldl -lm; the C feature-test macros
    (_GNU_SOURCE) are now in el_runtime.c itself.

  - build.sh: stages the foundation El runtime into ./runtime/, runs
    elc to regenerate server.c, builds the docker image. --tag and
    --push flags. Push targets us-central1-docker.pkg.dev/neuron-785695/
    neuron-marketing/marketing for the Cloud Run flip (still manual).

  - .gitignore: runtime/, /server.c, build/ — all build artifacts.

The path here was non-trivial. The original goal was to compile the
full 4325-line landing-combined.el end-to-end; that OOM'd at 8.7 GB
under the always-allocate-fresh el_list_append (the workaround for an
aliasing bug in cg_if_stmt). The runtime ARC scaffolding committed
earlier today got the compile down to 3.5 GB peak in 0.26s, but the
landing-combined still has pre-existing source bugs (http_serve(3001)
arity, neuron_origin bare expression statement) that block the build.
The structurally cleaner path was to render the HTML once, offline, and
serve the static output — which is what this server.el does. The
landing-combined.el can be revisited when those source bugs are fixed;
this server.el is the canonical production surface in the meantime.

Did not commit ./runtime/ (gitignored, staged from foundation by
build.sh on each build), ./server.c (generated by elc from server.el),
or ./build/ (build artifacts). The repo carries the source of truth
only.
2026-04-30 18:15:27 -05:00

64 lines
2.5 KiB
Docker

# Neuron Landing — El-native server.
#
# Two-stage build:
# 1. Build the El landing binary in a Debian container with cc + libcurl-dev
# from server.c (which was generated on the host by `elc server.el > server.c`)
# plus el_runtime.c.
# 2. Copy the binary + the pre-rendered index.html + assets into a slim runtime
# image. Final image is ~80 MB (mostly libc + libcurl).
#
# Build:
# ./build.sh (regenerates server.c, then docker buildx for linux/amd64)
#
# Run:
# docker run -p 8080:8080 neuron-landing
# ── Stage 1: compile ──────────────────────────────────────────────────────────
FROM debian:bookworm-slim AS builder
RUN apt-get update \
&& apt-get install -y --no-install-recommends \
build-essential \
libcurl4-openssl-dev \
ca-certificates \
&& rm -rf /var/lib/apt/lists/*
WORKDIR /build
COPY runtime/el_runtime.c runtime/el_runtime.h ./
COPY server.c ./
# -rdynamic is the Linux-specific bit: the runtime resolves El handler
# functions (e.g. handle_request) via dlsym(RTLD_DEFAULT, name), and on
# glibc that only sees the executable's own symbols if they were exported
# by the linker. macOS exports them by default, Linux doesn't.
RUN cc -std=c11 -O2 -rdynamic -I . -o landing server.c el_runtime.c -lcurl -lpthread -ldl -lm
# `strip` would discard .symtab but keeps .dynsym (which is what -rdynamic
# populated and what dlsym actually looks at), so it'd be safe — but the
# binary is small enough that the few MB saved isn't worth the next person
# wondering why dlsym fails.
# ── Stage 2: runtime ──────────────────────────────────────────────────────────
FROM debian:bookworm-slim
RUN apt-get update \
&& apt-get install -y --no-install-recommends \
libcurl4 \
ca-certificates \
&& rm -rf /var/lib/apt/lists/* \
&& groupadd -r landing && useradd -r -g landing landing
COPY --from=builder /build/landing /usr/local/bin/landing
COPY src/index.html /srv/landing/index.html
COPY src/assets /srv/landing/assets
ENV LANDING_ROOT=/srv/landing
ENV PORT=8080
USER landing
EXPOSE 8080
# Cloud Run sends SIGTERM on revision shutdown. The runtime doesn't trap it
# explicitly, so the kernel just kills the process. That's fine for a stateless
# server.
CMD ["/usr/local/bin/landing"]