Repository navigation
feat(server): add registry commands to manage Docker logins - #100
Merged
Merged
Conversation
Add `coolify server registry` with list, login, check and logout subcommands for managing Docker registry logins on servers. - list shows the registries each server is logged in to and the resources that use them. Usernames are masked unless -s is given. - login runs docker login on one or more servers. The password is read from --password-stdin or prompted without echo, and is limited to 20000 bytes. - check confirms that a saved login still works. - logout runs docker logout, with -f to skip the confirmation prompt. - Registry input is normalized (scheme, case and path are stripped) before it is used as a URL path segment. - Debug logs of API requests now redact "password" fields.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
coolify server registrycommand group (aliasregistries) for managing Docker registry logins on servers:list <server_uuid>shows the registries the server is logged in to, their status (Logged in / Credential helper / Not logged in), and a summary of which resources use them, such as "3 applications, 1 database". Usernames are hidden in table output unless-sis passed. JSON output includes the fullused_bydetails. If the API returns anerrorfield, it is printed as a warning. This command needs a token withread:sensitive.login <server_uuid> [<server_uuid>...]runsdocker loginon one or more servers using--registryand-u/--username. When logging in to several servers, each result is reported separately and the command fails with a summary if any server failed.check <server_uuid> <registry>checks that the saved login still works.logout <server_uuid> <registry>runsdocker logout. It asks for confirmation unless-f/--forceis given.--password-stdin, which strips only one trailing newline likedocker login. Otherwise it is read from a hidden prompt when running in a terminal. The password is sent only in the JSON request body and is capped at 20,000 bytes to match the API limit.https://GHCR.io/becomesghcr.io. Registry values are escaped as a single URL path segment, and hosts with ports likeregistry.example.com:5000work.passwordfields as well astokenfields.README.mdandllms-full.txtwith the new commands.