The console writes .well-known/source (https://coffeylabs.org/specs/well-known-source/) into dist/ when the build is given its commit in INBUXA_REVISION: name, version, license, repository, revision.
docker/nginx.conf serves that path exactly, as JSON with no-cache and open CORS; a build without it answers 404 instead of falling through to the app.
The Dockerfile takes INBUXA_REVISION as a build arg; both image builds pass the commit.
Checked: unit tests; typecheck, lint, i18n:check, full tests (951) and build; the image built with a revision serves the document (GET/HEAD 200), built without one answers 404.
Production builds the console on its host, not from this image, so the deploy there passes the commit and its nginx gets the same location; I'll do that with the deploy.
The console writes `.well-known/source` (https://coffeylabs.org/specs/well-known-source/) into `dist/` when the build is given its commit in `INBUXA_REVISION`: name, version, license, repository, revision.
- `docker/nginx.conf` serves that path exactly, as JSON with `no-cache` and open CORS; a build without it answers 404 instead of falling through to the app.
- The Dockerfile takes `INBUXA_REVISION` as a build arg; both image builds pass the commit.
- Checked: unit tests; typecheck, lint, i18n:check, full tests (951) and build; the image built with a revision serves the document (GET/HEAD 200), built without one answers 404.
Production builds the console on its host, not from this image, so the deploy there passes the commit and its nginx gets the same location; I'll do that with the deploy.
The console's public repository and the commit it was built from, in
the form https://coffeylabs.org/specs/well-known-source/ defines. The
commit comes from INBUXA_REVISION, which the image build passes in; a
build without one writes nothing, and nginx answers that address with a
404 rather than the app. tsconfig.node.json drops source-archive.ts,
gone since #7.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The console writes
.well-known/source(https://coffeylabs.org/specs/well-known-source/) intodist/when the build is given its commit inINBUXA_REVISION: name, version, license, repository, revision.docker/nginx.confserves that path exactly, as JSON withno-cacheand open CORS; a build without it answers 404 instead of falling through to the app.INBUXA_REVISIONas a build arg; both image builds pass the commit.Production builds the console on its host, not from this image, so the deploy there passes the commit and its nginx gets the same location; I'll do that with the deploy.