tr-gitlab
https://docs.gitlab.com/ee/user/packages/container_registry/...
That restriction is something we will be moving away from in the coming months. I like how GitHub allows you to publish an image under a namespace. We have an open issue for that: https://gitlab.com/gitlab-org/gitlab/-/issues/241027.
As a workaround, you can add your access token as an environment variable and use that to publish/install packages via CI/CD.
And if you are interested in contributing to GitLab that issue is a great way get started.
This means that for npm, Maven, NuGet, Conan and any future formats, you will be able to:
- Establish GitLab as a private repository - Authenticate using your GitLab credentials, personal access or job token - Publish packages to GitLab - Pull packages from GitLab - Search for packages hosted on GitLab - Access an easy-to-use UI that displays package details and metadata and allows you to download any relevant files
It does take a bit of work to migrate the code. We are currently investigating what work is required and will have a better sense of timing once the investigation is complete. We are hoping to have this complete in the next few months.
You can follow along in the issue here: https://gitlab.com/groups/gitlab-org/-/epics/2867.
At GitLab, the CE edition currently offers a container registry, that allows users to build, push and share images using the Docker client and/or GitLab CI/CD.
The EE edition offers an NPM and Maven registry, that allows users to publish, download and share dependencies. Both also integrate with GitLab CI/CD. We are currently working on Conan (C/C++) and NuGet (.NET). We are evaluating moving these features to CE as well.
We also offer a proxy to for Docker images (which will be extended to each registry) that improves reliability and performance and (in the future) will help mitigate and remediate open source risk.
If you end up trying GitHub's registry, I'd love to hear more about what you thought.
Aside from the benefits of being able to be around more with my family and to better handle life events, I've found that I enjoying working this way much more.
Working asynchronously forces people to really think about how and what they communicate. I've found that people, including myself, are much more prepared and thoughtful in their work.
I also find that there are way less distractions and that meetings with my coworkers are much more enjoyable. I thought I would have a hard time with the random 'coffee chat' but have come to really value them. It's a great way to be social and meet people, without the pressure of having to do it every day.
If you have any questions or feedback, you can email me at at [email protected]. I'd love to hear more about how you are using the docker registry today and any improvements you'd like to see made to the product.