mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #527] Also provide alternate image registry to ghcr? #193
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#193
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @budimanjojo on GitHub (Apr 5, 2023).
Original GitHub issue: https://github.com/lldap/lldap/issues/527
Hello! Thanks for this amazing project!
Dockerhub's rate limits (100/6hours pull actions) is frustrating to deal with when you have a lot of containers. It would be great to also host the images on
ghcror maybequay.io. The implementation should also be pretty easy looking at the current workflow that push the images. I believe it's as simple as adding these lines to this file: https://github.com/lldap/lldap/blob/main/.github/workflows/docker-build-static.ymlBelow this:
github.com/lldap/lldap@86b2b5148d/.github/workflows/docker-build-static.yml (L469-L474)add:And in every line like this:
github.com/lldap/lldap@86b2b5148d/.github/workflows/docker-build-static.yml (L487)change them to something like this:
I can do a PR if you don't have time to do this. Thanks before.
@budimanjojo commented on GitHub (Apr 5, 2023):
Just realize there's already a PR for this: https://github.com/lldap/lldap/pull/470
Maybe I can help with the
I think we should rather incorporate this into the other docker workflow, so we don't have to repeat the work. In addition, it'll support the various architectures that we do.comment there.@nitnelave commented on GitHub (Apr 5, 2023):
Feel free to take over the PR or create a new one, I think it was abandoned by the author.
Also, I don't know how much that changes, but keep in mind that I'd like to migrate to push to both nitnelave/lldap and lldap/lldap.
@budimanjojo commented on GitHub (Apr 5, 2023):
Thanks! I can do the PR, but to be able to push to
nitnelave/lldapyou might need to setup a GH secret for that username, maybe I can create PR to push toghcr.io/lldap/lldapand you can change that toghcr.io/nitnelave/lldapby yourself by changing the login username and password workflow step later?@nitnelave commented on GitHub (Apr 5, 2023):
Yeah, I can take care of setting up any secret that's needed. Just highlight them in the PR.
@budimanjojo commented on GitHub (Apr 5, 2023):
I created the PR. Can u have a look? Thanks before.