Alternatives to GitPlex logo

Alternatives to GitPlex

GitHub, GitLab, Bitbucket, GitHub Enterprise, and AWS CodeCommit are the most popular alternatives and competitors to GitPlex.
1
19
+ 1
0

What is GitPlex and what are its top alternatives?

GitPlex mimics git log in web interface, with hints and auto-completes available to help user quickly constructing desired commit queries.
GitPlex is a tool in the Code Collaboration & Version Control category of a tech stack.

Top Alternatives to GitPlex

  • 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. ...

  • GitLab
    GitLab

    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers. ...

  • Bitbucket
    Bitbucket

    Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users. ...

  • GitHub Enterprise
    GitHub Enterprise

    GitHub Enterprise lets developers use the tools they love across the development process with support for popular IDEs, continuous integration tools, and hundreds of third party apps and services. ...

  • AWS CodeCommit
    AWS CodeCommit

    CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools. ...

  • JFrog Artifactory
    JFrog Artifactory

    It integrates with your existing ecosystem supporting end-to-end binary management that overcomes the complexity of working with different software package management systems, and provides consistency to your CI/CD workflow. ...

  • Gitea
    Gitea

    Gitea is a community managed lightweight code hosting solution written in Go. It published under the MIT license. ...

  • Gogs
    Gogs

    The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows. ...

GitPlex alternatives & related posts

GitHub logo

GitHub

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

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
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.2M 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
GitLab logo

GitLab

47.7K
39.8K
2.3K
Open source self-hosted Git management software
47.7K
39.8K
+ 1
2.3K
PROS OF GITLAB
  • 497
    Self hosted
  • 423
    Free
  • 335
    Has community edition
  • 239
    Easy setup
  • 238
    Familiar interface
  • 131
    Includes many features, including ci
  • 108
    Nice UI
  • 81
    Good integration with gitlabci
  • 54
    Simple setup
  • 33
    Has an official mobile app
  • 32
    Free private repository
  • 29
    Continuous Integration
  • 19
    Open source, great ui (like github)
  • 15
    Slack Integration
  • 11
    Full CI flow
  • 10
    Free and unlimited private git repos
  • 8
    User, group, and project access management is simple
  • 7
    Built-in CI
  • 7
    Intuitive UI
  • 7
    All in one (Git, CI, Agile..)
  • 4
    Both public and private Repositories
  • 3
    Integrated Docker Registry
  • 3
    Mattermost Chat client
  • 3
    Issue system
  • 2
    One-click install through DigitalOcean
  • 2
    Dockerized
  • 2
    Because is the best remote host for git repositories
  • 2
    Full DevOps suite with Git
  • 2
    Free private repos
  • 2
    Great for team collaboration
  • 2
    Unlimited free repos & collaborators
  • 2
    It's fully integrated
  • 2
    I like the its runners and executors feature
  • 2
    CI
  • 2
    So easy to use
  • 2
    It's powerful source code management tool
  • 2
    Excellent
  • 2
    Build/pipeline definition alongside code
  • 2
    Security and Stable
  • 2
    Low maintenance cost due omnibus-deployment
  • 2
    On-premises
  • 1
    Multilingual interface
  • 1
    Kubernetes integration with GitLab CI
  • 1
    Review Apps feature
  • 1
    Powerful software planning and maintaining tools
  • 1
    Groups of groups
  • 1
    Built-in Docker Registry
  • 1
    Beautiful
  • 1
    Wounderful
  • 1
    Opensource
  • 1
    Not Microsoft Owned
  • 1
    Many private repo
  • 1
    Published IP list for whitelisting (gl-infra#434)
  • 1
    The dashboard with deployed environments
  • 1
    HipChat intergration
  • 1
    Kubernetes Integration
  • 1
    Native CI
  • 1
    Powerful Continuous Integration System
  • 1
    It includes everything I need, all packaged with docker
  • 0
    Supports Radius/Ldap & Browser Code Edits
CONS OF GITLAB
  • 27
    Slow ui performance
  • 7
    Introduce breaking bugs every release
  • 5
    Insecure (no published IP list for whitelisting)
  • 1
    Built-in Docker Registry
  • 0
    Review Apps feature

related GitLab posts

Tim Abbott
Shared insights
on
GitHubGitHubGitLabGitLab
at

I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

  • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
  • You can't let anyone with a GitHub account self-assign issues to themselves.
  • Many more similar issues.

It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

See more
Joshua Dean Küpper
CEO at Scrayos UG (haftungsbeschränkt) · | 20 upvotes · 361.5K views

We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

See more
Bitbucket logo

Bitbucket

34.2K
27.1K
2.8K
One place to plan projects, collaborate on code, test and deploy, all with free private repositories
34.2K
27.1K
+ 1
2.8K
PROS OF BITBUCKET
  • 905
    Free private repos
  • 398
    Simple setup
  • 347
    Nice ui and tools
  • 341
    Unlimited private repositories
  • 240
    Affordable git hosting
  • 123
    Integrates with many apis and services
  • 119
    Reliable uptime
  • 86
    Nice gui
  • 84
    Pull requests and code reviews
  • 58
    Very customisable
  • 16
    Mercurial repositories
  • 14
    SourceTree integration
  • 11
    JIRA integration
  • 10
    Track every commit to an issue in JIRA
  • 8
    Best free alternative to Github
  • 8
    Deployment hooks
  • 7
    Automatically share repositories with all your teammates
  • 7
    Compatible with Mac and Windows
  • 6
    Source Code Insight
  • 5
    Price
  • 5
    Login with Google
  • 5
    Create a wiki
  • 5
    Approve pull request button
  • 4
    Customizable pipelines
  • 4
    #2 Atlassian Product after JIRA
  • 3
    Continuous Integration and Delivery
  • 3
    Unlimited Private Repos at no cost
  • 3
    Also supports Mercurial
  • 2
    Teamcity
  • 2
    Mercurial Support
  • 2
    IAM
  • 2
    Issues tracker
  • 2
    Open source friendly
  • 2
    Multilingual interface
  • 2
    Academic license program
  • 2
    IAM integration
  • 0
    Free Private Repositories
CONS OF BITBUCKET
  • 19
    Not much community activity
  • 17
    Difficult to review prs because of confusing ui
  • 15
    Quite buggy
  • 10
    Managed by enterprise Java company
  • 8
    CI tool is not free of charge
  • 7
    Complexity with rights management
  • 6
    Only 5 collaborators for private repos
  • 4
    Slow performance
  • 2
    No AWS Codepipelines integration
  • 1
    No more Mercurial repositories
  • 1
    No server side git-hook support

related Bitbucket posts

Michael Kelly
Senior Software Engineer at StackShare · | 14 upvotes · 674.7K views

I use GitLab when building side-projects and MVPs. The interface and interactions are close enough to those of GitHub to prevent cognitive switching costs between professional and personal projects hosted on different services.

GitLab also provides a suite of tools including issue/project management, CI/CD with GitLab CI, and validation/landing pages with GitLab Pages. With everything in one place, on an #OpenSourceCloud GitLab makes it easy for me to manage much larger projects on my own, than would be possible with other solutions or tools.

It's petty I know, but I can also read the GitLab code diffs far more easily than diffs on GitHub or Bitbucket...they just look better in my opinion.

See more
Shared insights
on
GitHubGitHubGitLabGitLabBitbucketBitbucket

A bit difference in GitHub and GitLab though both are Version Control repository management services which provides key component in the software development workflow. A decision of choosing GitHub over GitLab is major leap extension from code management, to deployment and monitoring alongside looking beyond the code base hosting provided best fitted tools for developer communities.

  • Authentication stages - With GitLab you can set and modify people’s permissions according to their role. In GitHub, you can decide if someone gets a read or write access to a repository.
  • Built-In Continuous Integrations - GitLab offers its very own CI for free. No need to use an external CI service. And if you are already used to an external CI, you can obviously integrate with Jenkins, etc whereas GitHub offers various 3rd party integrations – such as Travis CI, CircleCI or Codeship – for running and testing your code. However, there’s no built-in CI solution at the moment.
  • Import/Export Resources - GitLab offers detailed documentation on how to import your data from other vendors – such as GitHub, Bitbucket to GitLab. GitHub, on the other hand, does not offer such detailed documentation for the most common git repositories. However, GitHub offers to use GitHub Importer if you have your source code in Subversion, Mercurial, TFS and others.

Also when it comes to exporting data, GitLab seems to do a pretty solid job, offering you the ability to export your projects including the following data:

  • Wiki and project repositories
  • Project uploads
  • The configuration including webhooks and services
  • Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities.

GitHub, on the other hand, seems to be more restrictive when it comes to export features of existing GitHub repositories. * Integrations - #githubmarketplace gives you an essence to have multiple and competitive integrations whereas you will find less in the GitLab.

So go ahead with better understanding.

See more
GitHub Enterprise logo

GitHub Enterprise

498
590
9
The on-premises version of GitHub, which you can deploy and manage in your own, secure environment
498
590
+ 1
9
PROS OF GITHUB ENTERPRISE
  • 3
    Expensive - $$$
  • 2
    Code security
  • 2
    CDCI with Github Actions
  • 1
    Both Cloud and Enterprise Server Versions available
  • 1
    Draft Pull Request
  • 0
    User experience
CONS OF GITHUB ENTERPRISE
  • 2
    $$$

related GitHub Enterprise posts

Matanel Crown
Software Developer at BBT.live · | 7 upvotes · 106.1K views

Hi all,

I would like some information regarding the benefits an aspiring start-up company may have, while using GitHub Enterprise vs the regular GitHub package. On a separate issue, I'd like to understand whether GitLab may have some DevOps-related advantages GitHub does not.

Thank you in advance, Matt

See more
Eric Seibert
DevOps at Children's Hospital of Philadelphia · | 6 upvotes · 179.8K views

We are using a Bitbucket server, and due to migration efforts and new Atlassian community license changes, we need to move to a new self-hosted solution. The new data-center license for Atlassian, available in February, will be community provisioned (free). Along with that community license, other technologies will be coming with it (Crucible, Confluence, and Jira). Is there value in a paid-for license to get the GitHub Enterprise? Are the tools that come with it worth the cost?

I know it is about $20 per 10 seats, and we have about 300 users. Have other convertees to Microsoft's tools found it easy to do a migration? Is the toolset that much more beneficial to the free suite that one can get from Atlassian?

So far, free seems to be the winner, and the familiarization with Atlassian implementation and maintenance is understood. Going to GitHub, are there any distinct challenges to be found or any perks to be attained?

See more
AWS CodeCommit logo

AWS CodeCommit

304
695
189
Fully-managed source control service that makes it easy for companies to host secure and highly scalable private Git...
304
695
+ 1
189
PROS OF AWS CODECOMMIT
  • 43
    Free private repos
  • 26
    IAM integration
  • 23
    Pay-As-You-Go Pricing
  • 19
    Repo data encrypted at rest
  • 19
    Amazon feels the most Secure
  • 11
    I can make repository by myself if I have AWS account
  • 11
    Faster deployments when using other AWS services
  • 7
    AWS CodePipeline integration
  • 6
    Codebuild integration
  • 6
    Does not support web hooks yet! :(
  • 4
    Cost Effective
  • 2
    Elastic Beanstalk Integration
  • 2
    Integrated with AWS Ecosystem
  • 2
    No Git LFS! Dealbreaker for me
  • 1
    Integration via SQS/SNS for events (replaces webhooks)
  • 1
    Issue tracker
  • 1
    IAM
  • 1
    Only US Region
  • 1
    Available in Ireland (Dublin) region
  • 1
    CodeDeploy Integration
  • 1
    Open source friendly
  • 1
    CodeCommit Trigger for an AWS Lambda Function
  • 0
    Ui
CONS OF AWS CODECOMMIT
  • 11
    UI sucks
  • 4
    SLOW
  • 3
    No Issue Tracker
  • 2
    Bad diffing/no blame
  • 2
    No fork
  • 2
    No webhooks
  • 2
    NO LFS support
  • 1
    Can't download file from UI
  • 1
    Only time based triggers
  • 0
    Accident-prone UI

related AWS CodeCommit posts

Hi, I need advice. In my project, we are using Bitbucket hosted on-prem, Jenkins, and Jira. Also, we have restrictions not to use any plugins for code review, code quality, code security, etc., with bitbucket. Now we want to migrate to AWS CodeCommit, which would mean that we can use, let's say, Amazon CodeGuru for code reviews and move to AWS CodeBuild and AWS CodePipeline for build automation in the future rather than using Jenkins.

Now I want advice on below.

  1. Is it a good idea to migrate from Bitbucket to AWS Codecommit?
  2. If we want to integrate Jira with AWS Codecommit, then how can we do this? If a developer makes any changes in Jira, then a build should be triggered automatically in AWS and create a Jira ticket if the build fails. So, how can we achieve this?
See more

Mojolicious Perl Redmine Redis AWS CodeCommit Amazon SES PostgreSQL Postman Docker jQuery VirtualBox Sublime Text GitHub Git GitLab CI @DBIx::Class @metacpan @TheBat

See more
JFrog Artifactory logo

JFrog Artifactory

292
306
0
Enterprise Universal Repository Manager
292
306
+ 1
0
PROS OF JFROG ARTIFACTORY
    Be the first to leave a pro
    CONS OF JFROG ARTIFACTORY
      Be the first to leave a con

      related JFrog Artifactory posts

      Joshua Dean Küpper
      CEO at Scrayos UG (haftungsbeschränkt) · | 10 upvotes · 205.1K views

      We use Sonatype Nexus to store our closed-source java libraries to simplify our deployment and dependency-management. While there are many alternatives, most of them are expensive ( GitLab Enterprise ), monilithic ( JFrog Artifactory ) or only offer SaaS-licences. We preferred the on-premise approach of Nexus and therefore decided to use it.

      We exclusively use the Maven-capabilities and are glad that the modular design of Nexus allows us to run it very lightweight.

      See more

      Whenever Qualys scan finds out software vulnerability, say for example Java SDK or any software version that has a potential vulnerability, we search the web to find out the solution and usually install a later version or patch downloading from the web. The problem is, as we are downloading it from web and there are a number of servers where we patch and as an ultimate outcome different people downloads different version and so forth. So I want to create a repository for such binaries so that we use the same patch for all servers.

      When I was thinking about the repo, obviously first thought came as GitHub.. But then I realized, it is for code version control and collaboration, not for the packaged software. The other option I am thinking is JFrog Artifactory which stores the binaries and the package software.

      What is your recommendation?

      See more
      Gitea logo

      Gitea

      221
      362
      109
      A painless self-hosted Git service
      221
      362
      + 1
      109
      PROS OF GITEA
      • 21
        Self-hosted
      • 14
        Lightweight
      • 14
        Free
      • 11
        Simple
      • 9
        Multiple code maintainers
      • 8
        Easy Setup
      • 6
        Pull requests and code reviews
      • 5
        Squash and Merge is supported
      • 5
        Import existing git repositories
      • 5
        Written in Go
      • 4
        Nice gui
      • 3
        Run in Raspberry Pi
      • 2
        LDAP Support
      • 2
        Community-fork of Gogs
      CONS OF GITEA
      • 3
        Community-fork of Gogs
      • 0
        Easy Windows authentication is not supported

      related Gitea posts

      Gogs logo

      Gogs

      161
      272
      182
      A self-hosted Git service written in Go
      161
      272
      + 1
      182
      PROS OF GOGS
      • 36
        Self-hosted github like service
      • 31
        Very low memory footprint
      • 29
        Easy to install / update
      • 17
        Lightweight (low minimal req.) runs on Raspberry pi
      • 16
        Single binary deploy no dependencies
      • 14
        Open source
      • 12
        Cross platform (MacOS, Windows, Linux ...)
      • 11
        Wiki
      • 10
        Issue tracker
      • 3
        Great UI
      • 3
        LDAP Support
      CONS OF GOGS
        Be the first to leave a con

        related Gogs posts

        Russtopia Labs
        Sr. Doodad Imagineer at Russtopia Labs · | 5 upvotes · 173.3K views
        Shared insights
        on
        GogsGogsGitHubGitHubGolangGolangGitLabGitLab

        I installed Gogs after a few repos I planned to use on GitHub disappeared without explanation, and after Microsoft's acquisition of same, it made me think about the over-centralization of community-developed software. A self-hosted solution that enables easy point-and-click mirroring of important repositories for my projects, both in-house and 3rd-party, ensures I won't be bitten by upstream catastrophes. (So far, Microsoft's stewardship has been fine, but always be prepared). It's also a very nice way to host one's own private repos before they're ready for prime-time on github.

        Gogs is written in Go and is easy to install and configure, IMHO much more so than GitLab, though it's of course less feature-rich; the only major feature I wish Gogs had is an integrated code review tool, but the web plugin hypothes.is https://stackshare.io/hypothes-is/hypothes-is is quite suitable as a code review tool. Set up a group for each code review, and just highlight lines to add comments in pull request pages of Gogs.

        See more