Alternatives to Gitea logo

Alternatives to Gitea

Gogs, GitLab, Phabricator, Bitbucket, and GitHub are the most popular alternatives and competitors to Gitea.
199
304
+ 1
82

What is Gitea and what are its top alternatives?

Gitea is a community managed lightweight code hosting solution written in Go. It published under the MIT license.
Gitea is a tool in the Code Collaboration & Version Control category of a tech stack.
Gitea is an open source tool with 27K GitHub stars and 3.4K GitHub forks. Here’s a link to Gitea's open source repository on GitHub

Top Alternatives to Gitea

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

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

  • Phabricator

    Phabricator

    Phabricator is a collection of open source web applications that help software companies build better software. ...

  • 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

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

  • GitBucket

    GitBucket

    GitBucket provides a Github-like UI and features such as Git repository hosting via HTTP and SSH, repository viewer, issues, wiki and pull request. ...

  • Gitolite

    Gitolite

    Gitolite allows you to setup git hosting on a central server, with fine-grained access control and many more powerful features. Gitolite is an access control layer on top of git. ...

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

Gitea alternatives & related posts

Gogs logo

Gogs

155
253
182
A self-hosted Git service written in Go
155
253
+ 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
    LDAP Support
  • 3
    Great UI
CONS OF GOGS
    Be the first to leave a con

    related Gogs posts

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

    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
    GitLab logo

    GitLab

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

    Phabricator

    219
    294
    186
    Open Source, Software Development Platform
    219
    294
    + 1
    186
    PROS OF PHABRICATOR
    • 33
      Open Source
    • 29
      Code Review
    • 25
      Supports Git/Hg/SVN
    • 17
      Audit Source Code
    • 17
      Bug Tracking
    • 11
      Unlimited Repo Support
    • 10
      Software Engineering Platform
    • 10
      Super fast task creation
    • 9
      Flexible Project Management
    • 8
      Project Management
    • 5
      Self hosted
    • 4
      Building Better Software
    • 2
      Complete set for collaborating on software development
    • 2
      Best Integration with Gitlab
    • 1
      Straightforward code review process
    • 1
      Workflow
    • 1
      Very effective system, does all PM & code org needed
    • 1
      Powerful, Complete, Fast, Reliable and Open Source
    CONS OF PHABRICATOR
      Be the first to leave a con

      related Phabricator posts

      Bitbucket logo

      Bitbucket

      31.6K
      24.7K
      2.8K
      One place to plan projects, collaborate on code, test and deploy, all with free private repositories
      31.6K
      24.7K
      + 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
      • 14
        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 · 625.5K 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 logo

      GitHub

      187.2K
      153.8K
      10.2K
      Powerful collaboration, review, and code management for open source and private development projects
      187.2K
      153.8K
      + 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
      • 859
        Easy setup
      • 499
        Issue tracker
      • 482
        Great community
      • 478
        Remote team collaboration
      • 446
        Great way to share
      • 439
        Pull request and features planning
      • 142
        Just works
      • 128
        Integrated in many tools
      • 114
        Free Public Repos
      • 108
        Github Gists
      • 106
        Github pages
      • 81
        Easy to find repos
      • 60
        Open source
      • 58
        Easy to find projects
      • 56
        Network effect
      • 55
        It's free
      • 47
        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
      • 13
        Wide acceptance
      • 10
        Large community
      • 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
        Graphs
      • 5
        Smooth integration
      • 5
        Nice API
      • 5
        Integrations
      • 5
        It's awesome
      • 4
        Remarkable uptime
      • 4
        Hands down best online Git service available
      • 4
        Reliable
      • 3
        Easy to use and collaborate with others
      • 3
        CI Integration
      • 3
        Free HTML hosting
      • 3
        Loved by developers
      • 3
        Quick Onboarding
      • 3
        Security options
      • 3
        Simple but powerful
      • 3
        Uses GIT
      • 3
        Unlimited Public Repos at no cost
      • 3
        Version Control
      • 2
        Nice to use
      • 1
        Free private repos
      • 1
        Easy deployment via SSH
      • 1
        Beautiful
      • 1
        Owned by micrcosoft
      • 1
        Free HTML hostings
      • 1
        Self Hosted
      • 1
        All in one development service
      • 1
        Easy to use
      • 1
        Good tools support
      • 1
        Easy source control and everything is backed up
      • 1
        Leads the copycats
      • 1
        Never dethroned
      • 1
        Ci
      • 1
        Issues tracker
      • 1
        Easy and efficient maintainance of the projects
      • 1
        IAM
      • 1
        IAM integration
      • 0
        Profound
      • 0
        1
      CONS OF GITHUB
      • 46
        Owned by micrcosoft
      • 36
        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
      • 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 · | 28 upvotes · 3.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
      GitBucket logo

      GitBucket

      75
      146
      36
      The easily installable Github clone powered by Scala
      75
      146
      + 1
      36
      PROS OF GITBUCKET
      • 8
        Self hosted
      • 7
        Open source
      • 6
        Familiar interface
      • 5
        Scala
      • 5
        Simple setup
      • 2
        Cross platform
      • 1
        SSH keys
      • 1
        Gists
      • 1
        Free
      CONS OF GITBUCKET
        Be the first to leave a con

        related GitBucket posts

        Siddhant Sharma
        Tech Connoisseur at Channelize.io · | 2 upvotes · 19.3K views

        GitBucket React Native for Windows Node.js GitHub We at Channeize.io have launched #Webhooks with our API services recently. Webhooks are an important part that can help you in retaining customers o your platform. Triggered by any event called, webhooks are proven to be increasing the engagement rate to up to 18%. Take a look at how you can monetize your products leveraging webhooks

        #Webhooks #API #InAppChat #inappcommunication #ChatApi #Chatsdk

        See more
        Gitolite logo

        Gitolite

        34
        68
        12
        Setup git hosting on a central server, with fine-grained access control
        34
        68
        + 1
        12
        PROS OF GITOLITE
        • 5
          Easy setup
        • 4
          Fine-tuned per-branch permissions
        • 1
          Really easy setup
        • 1
          Free
        • 1
          Free multi-server mirroring
        CONS OF GITOLITE
        • 1
          Doesn't have any user interface
        • 1
          Antiquated
        • 1
          No tools for project and issue tracker

        related Gitolite posts

        Git logo

        Git

        136.4K
        111.8K
        6.6K
        Fast, scalable, distributed revision control system
        136.4K
        111.8K
        + 1
        6.6K
        PROS OF GIT
        • 1.4K
          Distributed version control system
        • 1.1K
          Efficient branching and merging
        • 964
          Fast
        • 846
          Open source
        • 728
          Better than svn
        • 368
          Great command-line application
        • 306
          Simple
        • 291
          Free
        • 232
          Easy to use
        • 222
          Does not require server
        • 27
          Distributed
        • 22
          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
          Github integration
        • 3
          Easy branching and merging
        • 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
        • 7
          Worst documentation ever possibly made
        • 5
          Awful merge handling
        • 3
          Unexistent preventive security flows
        • 3
          Rebase hell
        • 2
          When --force is disabled, cannot rebase
        • 2
          Ironically even die-hard supporters screw up badly

        related Git posts

        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.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
        Ali Soueidan
        Creative Web Developer at Ali Soueidan · | 18 upvotes · 800.6K views

        Application and Data: Since my personal website ( https://alisoueidan.com ) is a SPA I've chosen to use Vue.js, as a framework to create it. After a short skeptical phase I immediately felt in love with the single file component concept! I also used vuex for state management, which makes working with several components, which are communicating with each other even more fun and convenient to use. Of course, using Vue requires using JavaScript as well, since it is the basis of it.

        For markup and style, I used Pug and Sass, since they’re the perfect match to me. I love the clean and strict syntax of both of them and even more that their structure is almost similar. Also, both of them come with an expanded functionality such as mixins, loops and so on related to their “siblings” (HTML and CSS). Both of them require nesting and prevent untidy code, which can be a huge advantage when working in teams. I used JSON to store data (since the data quantity on my website is moderate) – JSON works also good in combo with Pug, using for loops, based on the JSON Objects for example.

        To send my contact form I used PHP, since sending emails using PHP is still relatively convenient, simple and easy done.

        DevOps: Of course, I used Git to do my version management (which I even do in smaller projects like my website just have an additional backup of my code). On top of that I used GitHub since it now supports private repository for free accounts (which I am using for my own). I use Babel to use ES6 functionality such as arrow functions and so on, and still don’t losing cross browser compatibility.

        Side note: I used npm for package management. 🎉

        *Business Tools: * I use Asana to organize my project. This is a big advantage to me, even if I work alone, since “private” projects can get interrupted for some time. By using Asana I still know (even after month of not touching a project) what I’ve done, on which task I was at last working on and what still is to do. Working in Teams (for enterprise I’d take on Jira instead) of course Asana is a Tool which I really love to use as well. All the graphics on my website are SVG which I have created with Adobe Illustrator and adjusted within the SVG code or by using JavaScript or CSS (SASS).

        See more