Serves /.well-known/source as https://coffeylabs.org/specs/well-known-source/ defines it: name, version, license, the public repository and the commit the build was made from. JSON, Cache-Control: no-cache, open CORS, anonymous rate limit like the other well-known endpoints.
The commit is compiled in from INBUXA_REVISION (types::branding::BUILD_REVISION). The Docker context has no .git, so the Dockerfile takes it as a build arg, and both publish paths pass the tag's commit (Gitea publish.yml, GitHub ci.yml).
No full commit id, no document: the address answers 404. Local cargo builds are unaffected.
Checked: unit tests for the document; a debug build with INBUXA_REVISION set, run on an empty store, answered GET and HEAD with 200 and the expected body; fork checks and cargo fmt --check clean.
Ships with the next server release; nothing to deploy on its own.
Serves `/.well-known/source` as https://coffeylabs.org/specs/well-known-source/ defines it: name, version, license, the public repository and the commit the build was made from. JSON, `Cache-Control: no-cache`, open CORS, anonymous rate limit like the other well-known endpoints.
- The commit is compiled in from `INBUXA_REVISION` (`types::branding::BUILD_REVISION`). The Docker context has no `.git`, so the Dockerfile takes it as a build arg, and both publish paths pass the tag's commit (Gitea `publish.yml`, GitHub `ci.yml`).
- No full commit id, no document: the address answers 404. Local `cargo build`s are unaffected.
- Checked: unit tests for the document; a debug build with `INBUXA_REVISION` set, run on an empty store, answered GET and HEAD with 200 and the expected body; fork checks and `cargo fmt --check` clean.
Ships with the next server release; nothing to deploy on its own.
The address https://coffeylabs.org/specs/well-known-source/ defines:
the server's name, version and license, its public repository, and the
commit the build was made from. The release images get the commit as
INBUXA_REVISION, since their build context has no .git; a build without
a full commit id answers 404, as a repository without a revision
doesn't name the build.
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.
Serves
/.well-known/sourceas https://coffeylabs.org/specs/well-known-source/ defines it: name, version, license, the public repository and the commit the build was made from. JSON,Cache-Control: no-cache, open CORS, anonymous rate limit like the other well-known endpoints.INBUXA_REVISION(types::branding::BUILD_REVISION). The Docker context has no.git, so the Dockerfile takes it as a build arg, and both publish paths pass the tag's commit (Giteapublish.yml, GitHubci.yml).cargo builds are unaffected.INBUXA_REVISIONset, run on an empty store, answered GET and HEAD with 200 and the expected body; fork checks andcargo fmt --checkclean.Ships with the next server release; nothing to deploy on its own.