Skip to content

fix: bind public API to IPv4 #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fabiorosa merged 1 commit into from
Aug 10, 2026
Merged

fix: bind public API to IPv4 #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,5 +16,5 @@ COPY . .
RUN npm run build && npm --workspace @afterhook/console run build

ENV NODE_ENV=production
ENV HOST=::
ENV HOST=0.0.0.0
CMD ["node", "scripts/dist/start-service.js"]
3 changes: 2 additions & 1 deletion docs/DEPLOYMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,8 @@ scale claim.
The root `render.yaml` defines the Render resources and non-secret variables.
The root `Dockerfile` builds the release artifact. Set
`AFTERHOOK_SERVICE_ROLE=all` to start the three processes. The image binds the
API to `::` and gives the destination a separate loopback host and port.
API to `0.0.0.0` for Render's public proxy and gives the destination a separate
loopback host and port.

Configuration boundaries:

Expand Down
Loading