6 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
danamir	b5921292db	Trim DEPLOY.md: reverse proxy is managed separately, out of scope here	2026-08-06 14:46:58 +03:00
danamir	154411e7a4	Fix nginx crash-loop on a fully fresh docker compose up ... nginx resolves a plain `proxy_pass http://server:8080;` hostname once at config-load time. On a cold `docker compose up` that creates every container at once, the `server` container isn't always registered in Docker's embedded DNS yet by the time the client's nginx starts — nginx then fails immediately ("host not found in upstream") and doesn't retry, so it just crash-loops. Route the target through a variable instead (`set $upstream_server ...; proxy_pass $upstream_server;`) with an explicit `resolver`, which makes nginx resolve the hostname lazily per-request via Docker's DNS rather than once at startup. Also add `depends_on: [server]` on the client service so it at least doesn't start before the server container exists at all. Verified with repeated `docker compose down && docker compose up` cycles locally — this only reliably reproduced starting every container from nothing simultaneously, which prior local testing hadn't actually done (the server container had usually stayed running across rebuilds).	2026-08-06 14:44:52 +03:00
danamir	773dbb493e	Add production deployment guide and harden compose for it ... - docker-compose.yml: bind client/server ports to 127.0.0.1 only — the client container is the sole intended public entry point (it proxies /api/* to the server itself), a host-level nginx sits in front of it in production. Client__Origin now configurable via CLIENT_ORIGIN env var. - docs/DEPLOY.md: step-by-step for a fresh Linux target (Docker install, clone, .env secrets, nginx + certbot). - docs/CI-CD.md: runner registration for that same target machine, in "host" mode so the deploy step's `docker compose up -d` acts on the actual running stack.	2026-08-06 14:18:22 +03:00
danamir	dfbc43a43e	Make client API calls relative instead of hardcoded localhost:5144 ... The client always called a hardcoded http://localhost:5144, which only worked when browser and server shared the same "localhost" — breaks for any real remote deployment, since the browser would try to reach that port on the visitor's own machine instead of the actual server. Now every environment routes /api/* to the server under the same origin the page was loaded from, so the client code needs no per-environment URL: - Docker (client container's own nginx) proxies /api/ to the server container. - `npm run dev` (Vite) proxies /api to localhost:5144 via server.proxy. - Production nginx (reverse proxy + TLS) just needs to forward everything to the client container, which already knows how to route /api itself. Also incidentally removes CORS from the picture everywhere, since none of these setups make a cross-origin request anymore.	2026-08-06 14:15:15 +03:00
danamir	74497fa747	Add Gitea Actions CI/CD workflow ... On every push/PR: run Domain.Tests, then docker compose build to validate the full stack still builds. On push to master: also docker compose up -d to redeploy. COMPOSE_PROJECT_NAME is pinned to ruvdstests so a run from a runner-managed checkout always targets the existing stack/volumes instead of spinning up a duplicate under a different project name.	2026-08-06 13:57:57 +03:00
danamir	942dfc9c1a	Initial commit: standalone quiz-testing system ... Full-stack F# (Domain/Server/Client via Fable+Elmish+Feliz), PostgreSQL persistence via Dapper, Docker Compose deployment. Student quiz-taking flow with time-limit enforcement and focus-loss tracking, Teacher question bank and quiz builder with results analytics, Admin user management.	2026-08-06 12:36:16 +03:00