Difference between revisions of "Binary repository manager"
Jump to navigation
Jump to search
↑ https://about.gitlab.com/devops-tools/jfrog-artifactory-vs-gitlab.html
↑ https://docs.gitlab.com/ee/user/packages/container_registry/
↑ https://github.blog/2019-05-10-introducing-github-package-registry/
| Line 36: | Line 36: | ||
* <code>[[docker push]]</code>, <code>[[conan upload]]</code> | * <code>[[docker push]]</code>, <code>[[conan upload]]</code> | ||
* [[Artifact]] | * [[Artifact]] | ||
| − | * [[ | + | * [[Package manager]] |
== See also == | == See also == | ||
Revision as of 18:43, 4 August 2022
This article is a Draft. Help us to complete it.
- Apache Archiva
- Azure Artifacts
- CloudRepo
- Inedo's ProGet
- feedz.io
- JFrog Artifactory (2008-2009)
- GitLab (2011, GitLab itself)[1]: Maven, Docker[2], NPM.
- GitHub Package Registry [3], since May 2019.
- MyGet
- Sonatype Nexus repository manager
- Packagecloud
- Package Drone
- Pulp, open source.
- Google Artifact Registry
Characteristics
- High availability
- Multi-site replication
- Disaster recovery
- Scalability
- Deduplication (JFrog Artifactory)
Activities
- Review Jfrog artifactory vs GitLab comparison: https://about.gitlab.com/devops-tools/jfrog-artifactory-vs-gitlab.html
Related terms
See also
- Artifacts, Binary repository manager
- Container Registry: JFrog Container Registry, AWS ECR, Azure container registry, VMware Harbor Registry, Google Cloud Registry, Amazon Elastic Container Registry (ECR), GitLab container registry,
crane, gcr.io, ghcr.io - Binary repository manager: JFrog Artifactory, GitLab, GitHub and Nexus repository manager
- Package managers: dpkg, APT, RPM, YUM, DNF, homebrew, pkgutil, opkg, Helm, pkg and snap, npm, Aptitude, alien, Conan, CRAN, Chocolatey, NuGet, PackageKit, Wajig, pacman, PIP, Apache Ivy, List packages, List files in packages, Spack
- Registry, Container registry, infrastructure registry, OCI registry, Docker Hub
Advertising:
