list, get, create, update and delete any registry type the server's schema describes, naming objects by id or by key
snapshot writes the settings as a plan, with references by key so it moves between servers; apply makes a server match one, in reference order, changing only what the plan names
settings are reloaded after a change where the server didn't do it itself
CI and releases follow inbuxa-migrate: Gitea waits on GitHub's build, and v* tags publish Linux amd64 and arm64 archives with SHA256SUMS.
The first code for inbuxa-cli.
- list, get, create, update and delete any registry type the server's schema describes, naming objects by id or by key
- snapshot writes the settings as a plan, with references by key so it moves between servers; apply makes a server match one, in reference order, changing only what the plan names
- settings are reloaded after a change where the server didn't do it itself
CI and releases follow inbuxa-migrate: Gitea waits on GitHub's build, and v* tags publish Linux amd64 and arm64 archives with SHA256SUMS.
List, get, create, update and delete any registry type the server's schema
describes, naming objects by id or by key. snapshot writes the settings as
a plan with references by key; apply makes a server match one, in reference
order, changing only what the plan names. Settings are reloaded after a
change where the server didn't do it itself.
CI and releases follow inbuxa-migrate: Gitea waits on GitHub's build, and
v* tags publish Linux amd64 and arm64 archives with SHA256SUMS.
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 first code for inbuxa-cli.
CI and releases follow inbuxa-migrate: Gitea waits on GitHub's build, and v* tags publish Linux amd64 and arm64 archives with SHA256SUMS.