fix(tiles): configure R2 CDN base URL build argument to resolve production basemap 404 #120

New issue

Closed

opened 2026-10-15 05:51:37 +00:00 by yuris · 0 comments

yuris commented

2026-10-15 05:51:37 +00:00

Owner

What to build

Resolve the production 404 error when loading indonesia.pmtiles by configuring NEXT_PUBLIC_TILES_BASE_URL in Docker image compilation and providing a production default fallback to Cloudflare R2.

Root Cause

public/tiles/indonesia.pmtiles (81 MB) is deliberately gitignored to prevent committing large binary vector tile archives into git.
The basemap vector tile archive is already compiled and hosted on Cloudflare R2 at https://tiles.gambut.nokopia.com/tiles/indonesia.pmtiles (HTTP 200 with byte-range request support).
In Dockerfile and .forgejo/workflows/deploy.yml, NEXT_PUBLIC_TILES_BASE_URL is neither declared as a Docker build argument nor supplied during the image build.
Next.js inlines "" for NEXT_PUBLIC_TILES_BASE_URL during pnpm build, causing resolveTileUrl() in src/lib/gis/tile-url.ts to fall back to pmtiles:///tiles/indonesia.pmtiles.
The standalone container lacks public/tiles/indonesia.pmtiles, returning HTTP 404 when the client MapLibre instance attempts to fetch basemap tiles.

Technical specifications

Target files:
- Dockerfile: Declare ARG NEXT_PUBLIC_TILES_BASE_URL=https://tiles.gambut.nokopia.com/tiles and pass it to the builder stage as ENV NEXT_PUBLIC_TILES_BASE_URL=$NEXT_PUBLIC_TILES_BASE_URL.
- .forgejo/workflows/deploy.yml: Add build-args: NEXT_PUBLIC_TILES_BASE_URL=https://tiles.gambut.nokopia.com/tiles to docker/build-push-action.
- src/lib/gis/tile-url.ts: In production environments (process.env.NODE_ENV === "production"), default base to https://tiles.gambut.nokopia.com/tiles if NEXT_PUBLIC_TILES_BASE_URL is unset or empty, ensuring gitignored tile archives never fall back to the container in production.
- src/lib/gis/__tests__/tile-url.test.ts: Add test cases validating production fallback behavior and local development fallback isolation.

Acceptance criteria

Dockerfile and deploy.yml accept and pass NEXT_PUBLIC_TILES_BASE_URL.
resolveTileUrl("indonesia") resolves to pmtiles://https://tiles.gambut.nokopia.com/tiles/indonesia.pmtiles when built in production mode without explicit local overrides.
Local offline development (pnpm dev) continues to resolve to local pmtiles:///tiles/... when NEXT_PUBLIC_TILES_BASE_URL is not provided.
Production web deployment successfully renders the dark Protomaps basemap without 404 errors.
Vitest test suite passes with 100% success.

Authoritative Specifications & Reference Documentation

Titik Gambut Architecture: docs/ARCHITECTURE.md
Cloudflare R2 Tiles Endpoint: https://tiles.gambut.nokopia.com/tiles/indonesia.pmtiles
Tile URL Resolver Implementation: src/lib/gis/tile-url.ts

### What to build Resolve the production 404 error when loading `indonesia.pmtiles` by configuring `NEXT_PUBLIC_TILES_BASE_URL` in Docker image compilation and providing a production default fallback to Cloudflare R2. ### Root Cause 1. `public/tiles/indonesia.pmtiles` (81 MB) is deliberately gitignored to prevent committing large binary vector tile archives into git. 2. The basemap vector tile archive is already compiled and hosted on Cloudflare R2 at `https://tiles.gambut.nokopia.com/tiles/indonesia.pmtiles` (HTTP 200 with byte-range request support). 3. In `Dockerfile` and `.forgejo/workflows/deploy.yml`, `NEXT_PUBLIC_TILES_BASE_URL` is neither declared as a Docker build argument nor supplied during the image build. 4. Next.js inlines `""` for `NEXT_PUBLIC_TILES_BASE_URL` during `pnpm build`, causing `resolveTileUrl()` in `src/lib/gis/tile-url.ts` to fall back to `pmtiles:///tiles/indonesia.pmtiles`. 5. The standalone container lacks `public/tiles/indonesia.pmtiles`, returning HTTP 404 when the client MapLibre instance attempts to fetch basemap tiles. ### Technical specifications 1. **Target files**: - `Dockerfile`: Declare `ARG NEXT_PUBLIC_TILES_BASE_URL=https://tiles.gambut.nokopia.com/tiles` and pass it to the `builder` stage as `ENV NEXT_PUBLIC_TILES_BASE_URL=$NEXT_PUBLIC_TILES_BASE_URL`. - `.forgejo/workflows/deploy.yml`: Add `build-args: NEXT_PUBLIC_TILES_BASE_URL=https://tiles.gambut.nokopia.com/tiles` to `docker/build-push-action`. - `src/lib/gis/tile-url.ts`: In production environments (`process.env.NODE_ENV === "production"`), default `base` to `https://tiles.gambut.nokopia.com/tiles` if `NEXT_PUBLIC_TILES_BASE_URL` is unset or empty, ensuring gitignored tile archives never fall back to the container in production. - `src/lib/gis/__tests__/tile-url.test.ts`: Add test cases validating production fallback behavior and local development fallback isolation. ### Acceptance criteria - [x] `Dockerfile` and `deploy.yml` accept and pass `NEXT_PUBLIC_TILES_BASE_URL`. - [x] `resolveTileUrl("indonesia")` resolves to `pmtiles://https://tiles.gambut.nokopia.com/tiles/indonesia.pmtiles` when built in production mode without explicit local overrides. - [x] Local offline development (`pnpm dev`) continues to resolve to local `pmtiles:///tiles/...` when `NEXT_PUBLIC_TILES_BASE_URL` is not provided. - [x] Production web deployment successfully renders the dark Protomaps basemap without 404 errors. - [x] Vitest test suite passes with 100% success. --- ### Authoritative Specifications & Reference Documentation - **Titik Gambut Architecture**: [`docs/ARCHITECTURE.md`](https://git.nokopia.com/yuris/titik-gambut-next/src/branch/main/docs/ARCHITECTURE.md) - **Cloudflare R2 Tiles Endpoint**: `https://tiles.gambut.nokopia.com/tiles/indonesia.pmtiles` - **Tile URL Resolver Implementation**: [`src/lib/gis/tile-url.ts`](https://git.nokopia.com/yuris/titik-gambut-next/src/branch/main/src/lib/gis/tile-url.ts)

yuris added this to the Edge Infrastructure & CDN Delivery (Backend) milestone

2026-10-15 05:51:37 +00:00

yuris added the

backend

label

2026-10-15 05:51:37 +00:00

yuris referenced this issue from a pull request that will close it,

2026-10-15 06:24:06 +00:00

fix(tiles): configure R2 CDN base URL build argument and CORS rules #121

yuris closed this issue

2026-10-15 06:27:36 +00:00

yuris referenced this issue from a commit