Repository navigation
server-v0.8.0
·
10 commits
to main
since this release
- The bundle now publishes a single port (D62). Gitea's web UI moved behind the
proxy at/accounts/, so there is no second port to open, firewall, or
certificate — setSCRIPTICUS_PUBLIC_URL(orget-scripticus-svr --public-url) when the registry is not reached athttp://localhost:8000,
since Gitea builds its links from it. The instance is also retitled
Scripticus, which the bootstrap script applies. get-scripticus-svrasks for the administrator's account and the publishing
namespace separately (D61), creating the latter as a Gitea organisation owned
by the admin. Defaulting the namespace to whoever ran the installer would put
an individual's name in every package reference —phil-from-it/backup-rotate
instead ofacme-co/backup-rotate— which nothing can undo once published.
The minted token now carriesread:organizationso publishing to an
organisation works without a second trip to the web UI.- Added
get-scripticus-svr, a bootstrap script that stands a registry up in one
command —curl -fsSL <url> | sh(D61): it preflights the host, fetches the compose bundle, starts it,
and creates a Gitea admin account with a correctly-scoped publish token,
printing the password and token once. It refuses rather than repairs — an
existing directory, stack, or Gitea user stops the run. - The bundle's host port is now
${SCRIPTICUS_PORT}, defaulting to the
documented 8000, so a second stack can coexist with an existing one. - Documented the Gitea token scopes properly:
organization: Readis also needed
to publish under an organisation namespace, which the previous instructions
omitted. - Fixed the registry bundle's documented standup:
docker-compose.ymlbind-mounted
./proxy/Caddyfile, which does not exist for an operator who fetches only the
compose file as the README instructs — Docker created an empty directory at the
mount path and the proxy container failed to start. The Caddyfile is now an
inlineconfigsentry in the compose file, so the one-file standup works (D45).
Needs Docker Compose v2.23.1 or newer.
Full Changelog: client-v0.7.0...server-v0.8.0