Alternatives to CloudRepo logo

Alternatives to CloudRepo

Cloudsmith Package, Gemfury, aptly, fpm, and Conan are the most popular alternatives and competitors to CloudRepo.
1
2
+ 1
0

What is CloudRepo and what are its top alternatives?

Fully managed software component repositories. Provides maven artifact repositories as well as PyPi package repositories.
CloudRepo is a tool in the Hosted Package Repository category of a tech stack.

Top Alternatives to CloudRepo

  • Cloudsmith Package
    Cloudsmith Package

    Level up your DevOps! Streamline your software dependencies and artefacts with Enterprise-grade package management today. ...

  • Gemfury
    Gemfury

    Hosted service for your private and custom packages to simplify your deployment story. Once you upload your packages and enable your Gemfury repository, you can securely deploy any package to any host. Your private RubyGems, Python packages, and NPM modules will be safe and within reach on Gemfury. Install them to any machine in minutes without worrying about running and securing your own private repository.<br> ...

  • aptly
    aptly

    aptly is a swiss army knife for Debian repository management: it allows you to mirror remote repositories, manage local package repositories, take snapshots, pull new versions of packages along with dependencies, publish as Debian repository. ...

  • fpm
    fpm

    It helps you build packages quickly and easily (Packages like RPM and DEB formats). ...

  • Conan
    Conan

    Install or build your own packages for any platform. Conan also allows you to run your own server easily from the command line. ...

  • Packagist
    Packagist

    It is the main Composer repository. It aggregates public PHP packages installable with Composer. It lets you find packages and lets Composer know where to get the code from. You can use Composer to manage your project or libraries' dependencies ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

  • GitHub
    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

CloudRepo alternatives & related posts

Cloudsmith Package logo

Cloudsmith Package

9
0
Cloud-native Artifact Management
9
0
PROS OF CLOUDSMITH PACKAGE
    Be the first to leave a pro
    CONS OF CLOUDSMITH PACKAGE
      Be the first to leave a con

      related Cloudsmith Package posts

      Gemfury logo

      Gemfury

      23
      6
      Private ruby gem hosting
      23
      6
      PROS OF GEMFURY
      • 2
        Easy Setup
      • 2
        Easy Integration
      • 1
        Multiple Repository Types
      • 1
        APT repository
      CONS OF GEMFURY
        Be the first to leave a con

        related Gemfury posts

        Julien DeFrance
        Principal Software Engineer at Tophatter · | 6 upvotes · 11.7K views
        Shared insights
        on
        RubyRubyRailsRailsGemfuryGemfuryGitGit
        at

        Working with Ruby on Rails also means working with #RubyGems Most of the time, the community has some gems you can use and list down your #Gemfile. But sometimes, you also need to come up with your own proprietary ones to encapsulate and re-use some of your business logic.

        It is critical that such repositories and their source code remain private, secure. Even though your code shouldn't contain any credentials, this still applies to your gems' distribution channels. Unless for parts you've willingly open sourced, you don't want your intellectual property stolen.

        Rubygems.org therefore, not being an option for this use case, I faced two alternatives: accepting the overhead of maintaining my own gem server, or finding a service that does it for me.

        Obviously, the latter was the way to go:

        I chose Gemfury for its convenience, pricing model, and reliability.

        Gemfury also allowed me/my team to publish gems via different methods: file upload, SSH, HTTPS, or as simple as a Git push.

        See more
        aptly logo

        aptly

        19
        0
        Swiss army knife for Debian repository management
        19
        0
        PROS OF APTLY
          Be the first to leave a pro
          CONS OF APTLY
            Be the first to leave a con

            related aptly posts

            fpm logo

            fpm

            80
            2
            packaging made simple
            80
            2
            PROS OF FPM
            • 2
              Easy to use
            CONS OF FPM
              Be the first to leave a con

              related fpm posts

              Conan logo

              Conan

              84
              10
              C/C++ package manager
              84
              10
              PROS OF CONAN
              • 4
                Crossplatform builds
              • 3
                Easy to maintain used dependencies
              • 2
                Build recipes can be very flexble
              • 1
                Integrations with cmake, qmake and other build systems
              CONS OF CONAN
              • 1
                3rd party recipes can be flawed

              related Conan posts

              Packagist logo

              Packagist

              42
              0
              A default Composer package repository
              42
              0
              PROS OF PACKAGIST
                Be the first to leave a pro
                CONS OF PACKAGIST
                  Be the first to leave a con

                  related Packagist posts

                  Git logo

                  Git

                  299K
                  6.6K
                  Fast, scalable, distributed revision control system
                  299K
                  6.6K
                  PROS OF GIT
                  • 1.4K
                    Distributed version control system
                  • 1.1K
                    Efficient branching and merging
                  • 959
                    Fast
                  • 845
                    Open source
                  • 726
                    Better than svn
                  • 368
                    Great command-line application
                  • 306
                    Simple
                  • 291
                    Free
                  • 232
                    Easy to use
                  • 222
                    Does not require server
                  • 28
                    Distributed
                  • 23
                    Small & Fast
                  • 18
                    Feature based workflow
                  • 15
                    Staging Area
                  • 13
                    Most wide-spread VSC
                  • 11
                    Disposable Experimentation
                  • 11
                    Role-based codelines
                  • 7
                    Frictionless Context Switching
                  • 6
                    Data Assurance
                  • 5
                    Efficient
                  • 4
                    Just awesome
                  • 3
                    Easy branching and merging
                  • 3
                    Github integration
                  • 2
                    Compatible
                  • 2
                    Possible to lose history and commits
                  • 2
                    Flexible
                  • 1
                    Team Integration
                  • 1
                    Easy
                  • 1
                    Light
                  • 1
                    Fast, scalable, distributed revision control system
                  • 1
                    Rebase supported natively; reflog; access to plumbing
                  • 1
                    Flexible, easy, Safe, and fast
                  • 1
                    CLI is great, but the GUI tools are awesome
                  • 1
                    It's what you do
                  • 0
                    Phinx
                  CONS OF GIT
                  • 16
                    Hard to learn
                  • 11
                    Inconsistent command line interface
                  • 9
                    Easy to lose uncommitted work
                  • 8
                    Worst documentation ever possibly made
                  • 5
                    Awful merge handling
                  • 3
                    Unexistent preventive security flows
                  • 3
                    Rebase hell
                  • 2
                    Ironically even die-hard supporters screw up badly
                  • 2
                    When --force is disabled, cannot rebase
                  • 1
                    Doesn't scale for big data

                  related Git posts

                  Simon Reymann
                  Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.9M views

                  Our whole DevOps stack consists of the following tools:

                  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
                  • Respectively Git as revision control system
                  • SourceTree as Git GUI
                  • Visual Studio Code as IDE
                  • CircleCI for continuous integration (automatize development process)
                  • Prettier / TSLint / ESLint as code linter
                  • SonarQube as quality gate
                  • Docker as container management (incl. Docker Compose for multi-container application management)
                  • VirtualBox for operating system simulation tests
                  • Kubernetes as cluster management for docker containers
                  • Heroku for deploying in test environments
                  • nginx as web server (preferably used as facade server in production environment)
                  • SSLMate (using OpenSSL) for certificate management
                  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
                  • PostgreSQL as preferred database system
                  • Redis as preferred in-memory database/store (great for caching)

                  The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

                  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
                  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
                  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
                  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
                  • Scalability: All-in-one framework for distributed systems.
                  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
                  See more
                  Tymoteusz Paul
                  Devops guy at X20X Development LTD · | 23 upvotes · 10.2M views

                  Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

                  It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

                  I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

                  We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

                  If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

                  The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

                  Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

                  See more
                  GitHub logo

                  GitHub

                  288K
                  10.3K
                  Powerful collaboration, review, and code management for open source and private development projects
                  288K
                  10.3K
                  PROS OF GITHUB
                  • 1.8K
                    Open source friendly
                  • 1.5K
                    Easy source control
                  • 1.3K
                    Nice UI
                  • 1.1K
                    Great for team collaboration
                  • 868
                    Easy setup
                  • 504
                    Issue tracker
                  • 487
                    Great community
                  • 483
                    Remote team collaboration
                  • 449
                    Great way to share
                  • 442
                    Pull request and features planning
                  • 147
                    Just works
                  • 132
                    Integrated in many tools
                  • 122
                    Free Public Repos
                  • 116
                    Github Gists
                  • 113
                    Github pages
                  • 83
                    Easy to find repos
                  • 62
                    Open source
                  • 60
                    Easy to find projects
                  • 60
                    It's free
                  • 56
                    Network effect
                  • 49
                    Extensive API
                  • 43
                    Organizations
                  • 42
                    Branching
                  • 34
                    Developer Profiles
                  • 32
                    Git Powered Wikis
                  • 30
                    Great for collaboration
                  • 24
                    It's fun
                  • 23
                    Clean interface and good integrations
                  • 22
                    Community SDK involvement
                  • 20
                    Learn from others source code
                  • 16
                    Because: Git
                  • 14
                    It integrates directly with Azure
                  • 10
                    Standard in Open Source collab
                  • 10
                    Newsfeed
                  • 8
                    Fast
                  • 8
                    Beautiful user experience
                  • 8
                    It integrates directly with Hipchat
                  • 7
                    Easy to discover new code libraries
                  • 6
                    It's awesome
                  • 6
                    Smooth integration
                  • 6
                    Cloud SCM
                  • 6
                    Nice API
                  • 6
                    Graphs
                  • 6
                    Integrations
                  • 5
                    Hands down best online Git service available
                  • 5
                    Reliable
                  • 5
                    Quick Onboarding
                  • 5
                    CI Integration
                  • 5
                    Remarkable uptime
                  • 4
                    Security options
                  • 4
                    Loved by developers
                  • 4
                    Uses GIT
                  • 4
                    Free HTML hosting
                  • 4
                    Easy to use and collaborate with others
                  • 4
                    Version Control
                  • 4
                    Simple but powerful
                  • 4
                    Unlimited Public Repos at no cost
                  • 3
                    Nice to use
                  • 3
                    IAM
                  • 3
                    Ci
                  • 3
                    Easy deployment via SSH
                  • 2
                    Free private repos
                  • 2
                    Good tools support
                  • 2
                    All in one development service
                  • 2
                    Never dethroned
                  • 2
                    Easy source control and everything is backed up
                  • 2
                    Issues tracker
                  • 2
                    Self Hosted
                  • 2
                    IAM integration
                  • 2
                    Very Easy to Use
                  • 2
                    Easy to use
                  • 2
                    Leads the copycats
                  • 2
                    Free HTML hostings
                  • 2
                    Easy and efficient maintainance of the projects
                  • 2
                    Beautiful
                  • 1
                    Dasf
                  • 1
                    Profound
                  CONS OF GITHUB
                  • 55
                    Owned by micrcosoft
                  • 38
                    Expensive for lone developers that want private repos
                  • 15
                    Relatively slow product/feature release cadence
                  • 10
                    API scoping could be better
                  • 9
                    Only 3 collaborators for private repos
                  • 4
                    Limited featureset for issue management
                  • 3
                    Does not have a graph for showing history like git lens
                  • 2
                    GitHub Packages does not support SNAPSHOT versions
                  • 1
                    No multilingual interface
                  • 1
                    Takes a long time to commit
                  • 1
                    Expensive

                  related GitHub posts

                  Johnny Bell

                  I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

                  I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

                  I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

                  Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

                  Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

                  With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

                  If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

                  See more

                  Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

                  Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

                  Check Out My Architecture: CLICK ME

                  Check out the GitHub repo attached

                  See more