WorkClub Automation 1aea91da55 fix: Bind Next.js server to 0.0.0.0 for external access ...

The deployment was unreachable because the Next.js server was binding
to localhost:3000 (127.0.0.1) instead of 0.0.0.0, making it only
accessible inside the Docker container.

- Added HOSTNAME=0.0.0.0 to Dockerfile build and runtime stages
- Added HOSTNAME=0.0.0.0 to docker-compose.yml for nextjs service

This allows the server to accept connections from external hosts.

2026-03-20 13:29:21 +01:00

.gitea/workflows

fix(k8s): stabilize keycloak rollout and align CD deploy manifests

2026-03-13 06:25:07 +01:00

.sisyphus

fix(k8s): stabilize keycloak rollout and align CD deploy manifests

2026-03-13 06:25:07 +01:00

backend

feat: restrict admin access to club operations and rollout test environment

2026-03-18 09:08:45 +01:00

frontend

fix: Bind Next.js server to 0.0.0.0 for external access

2026-03-20 13:29:21 +01:00

infra

feat: restrict admin access to club operations and rollout test environment

2026-03-18 09:08:45 +01:00

openspec/changes/archive/2026-03-20-replace-uuids-with-names

fix: Bind Next.js server to 0.0.0.0 for external access

2026-03-20 13:29:21 +01:00

.editorconfig

chore(scaffold): initialize git repo and monorepo with .NET solution

2026-03-03 14:02:37 +01:00

.gitignore

chore(scaffold): initialize git repo and monorepo with .NET solution

2026-03-03 14:02:37 +01:00

docker-compose.yml

fix(auth): resolve Keycloak OIDC issuer mismatch and API proxy routing

2026-03-09 14:21:03 +01:00

S

Description

No description provided

3 MiB

Releases 1

Test Latest

2026-03-08 14:27:26 +01:00

Languages

HTML 54.2%

C# 27%

TypeScript 15.6%

Shell 1.7%

Python 0.7%

Other 0.7%