Docker Registry 2.0 VS Private Packagist

Run your own container registry, build and host everything yourself, dont rely on others. Docker for example has a option for that but imo its very basic and limited. Harbor is more advanced but still not overly complicated. You could add build workers to that and automate your entire pipeline, but maybe for a single image thats overkill. But good to have those options in the future. Things to look at for example:... Source: 10 months ago

You can run your own docker registry if you want and push images to it: https://docs.docker.com/registry/. Source: 10 months ago

You can self-host your own. There is many alternatives but the official one you can find in these docs here Https://docs.docker.com/registry/. Source: 12 months ago

Yes, this one https://docs.docker.com/registry/. Source: 12 months ago

Operate a pull-through cache registry, like Artifactory or the open source reference Docker registry. This will allow you to pull images from Docker Hub less frequently, improving your chances of staying under the anonymous usage limit. - Source: dev.to / about 1 year ago

I was told in another forum to look at Private Packagist... But how is that different? Instead of installing packages from packagist.org.. You pay to Packagist.com to do the same thing? You just download from packagist.com cloud instead of packagist.org? Source: over 1 year ago

We have a private Satis instance. Our ITSec team reviews all packages before we add them to Satis. Packagist.com is available for us but the CI-CD servers can reach only the private Satis. Source: almost 2 years ago

Https://packagist.com maybe tell them about a local packagist install. Source: almost 2 years ago

"[MANAGER] requested this to be done in PHP. You as IT will know that most modern programming and scripting languages work only with packaging software properly. Composer sends requests (majority of cases) to packagist.com and to github.com. It will add thousands of hours to do everything that composer does manually. Please sign here to authorize the usage of 4000 hours and the possible delay of 4000 hours.... Source: almost 2 years ago

Another downside that only really exists with non-PHP boilerplates is getting updates isn'T as easy. With PHP we're able to use packagist.com and make our code available via composer. Other languages don't have this so SaaS Pegasus provides zip downloads and Gravity provides access to a GitHub repo. This means you have to apply bug fixes yourself. With Parthenon, you do composer update and you'll get the latest... Source: almost 2 years ago