68ad014df0
`docker compose up` failed with "port is already allocated": 3000 was taken by an unrelated project on the same machine. Publishing it was never needed — in production the only thing that has to reach this service is the reverse proxy, which does so over the compose network as `landing:3000`. `expose` replaces `ports`, and a commented `ports` block stays for the cases that do want a host binding. LANDING_PORT is kept but re-labelled as only mattering then. Verified: the container binds nothing on the host, answers 200 with the full page from another container on the network, and stays healthy — its health check was always internal. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
22 lines
984 B
Plaintext
22 lines
984 B
Plaintext
# Copy to `.env`. Compose reads it on its own — for the runtime settings below
|
|
# and for the build-time token. `.env` is gitignored; this file is not.
|
|
|
|
# Base URL of the Pireon API, without a trailing slash. Read on the server only:
|
|
# the browser never talks to the API directly.
|
|
PIREON_API_URL=https://landing-api.pireon.dev/api
|
|
|
|
# Only used if you uncomment `ports` in docker-compose.yml. By default the
|
|
# container is not published on the host at all: the reverse proxy reaches it
|
|
# over the compose network as `landing:3000`, and publishing a host port only
|
|
# invites a collision with whatever else is on that number.
|
|
LANDING_PORT=3000
|
|
|
|
# Needed only to *build* the image: `@pi/ui` comes from the private Nexus.
|
|
# Locally this is the value already sitting in ~/.npmrc:
|
|
#
|
|
# grep nexus.pireon.dev ~/.npmrc
|
|
#
|
|
# Never baked into a layer — it is mounted as a BuildKit secret. An empty value
|
|
# fails the build immediately with an explanation rather than a Nexus 401.
|
|
NEXUS_TOKEN=
|