11
Bubbles
6d

Is it a good idea to use Github or have a private local Git Server? I’ve heard Github now let’s people make private repositories for free so I was thinking of that but idk. What do you guys use?

Comments
  • 5
    I've been using Bitbucket. I had a small victory recently when we started using it for our SQL scripts. Code is code regardless of how simple or complex it is, and version control is equally valid regardless of complexity. And I hate it when I get a call, "we need the ddl from this release..." when I can just tell the change managers, the golden copy can be found in this repo, and you can just copy it.
  • 3
    @iAmNaN do big/normal sized companies use their own version control servers or use gitlab github etc
  • 4
    @Bubbles we use Bitbucket Stash (Atlassian) locally, so our own servers. Can't speak for others.
  • 2
    Bitbucket works great.
  • 2
    @iAmNaN alright thank you :) I’m just tryin to get an idea on how companies do stuff so I’ll be prepared
  • 3
    @pai-shinoda yes. No complaints at all. It does all that we need, and is simple to use.
  • 3
    In our company we have our own git server [legal reasons], a gitlab server w/ all the automations and shit and some our clients store their code in other solutions, like their own TFS, bitbucket, etc.

    Haven't seen anyone store their code at 3rd parties, like gh.
  • 2
    GitLab
  • 2
    Gitlab +1
  • 2
    Private gitea instance
  • 2
    @Bubbles We use an on premise Gitlab at work. It just "works" and has the necessary feautes included (CI, docker registry, ...). As far I know, if you use public Github with private repositories this not (but at public Gitlab it is included).
    One small thing: Gitlab needs weekly security updates.
  • 2
    I do a self hosted gitlab server :)
  • 2
    As long as the repo is on another machine, all the solutions are valid.

    Ideally, for backup purposes, you should have your code:
    - on your machine
    - on a different machine (theft, hardware failure...)
    - in a different building (fire...)
    - in a different city (catastrophic events)

    From a maintenance perspective, I wouldn't go for a self hosted solution, unless you have constraints (technical or legal). You will have to maintain the server and that can take more time than you think. Also, you're more vulnerable to ransom attacks (happened to me with a mySQL server)
  • 1
    @netikras What is a Git server?
  • 1
    Let's pretend the question category doesn't exist...
  • 1
    Btw, if use github, can host pages.. 😅 usefull for quick publishing
  • 1
    Another wagon of the GitLab train here.
  • 1
    Doesn't matter which one (I use gitlab) , just don't bother hosting your own. It will only be time and effort to setup, maintain, keep running and will need to be back up anyway to the cloud unless you want to risk losing your repos if hard drive fails. Cloud all the way. Most small companies do this. Only big companies host their own usually
  • 1
    I setup bare git repo in company server only, don't know if it is correct setup for version control system
  • 1
    I personally would go for github/gitlab/gitbucket the simple reason one less service you'll have to maintain/update and if anything happens you have a remote backup (even if your house burns down).
  • 3
    @lukegv a server accessible via ssh, having git installed, a dedicated git user and repositories stored.
  • 2
    We have GitLab in a DMZ
  • 1
    Emailing patches 😎👌
  • 2
    At work we have a self hosted GitLab Server. For personal projects I use GitLab.com, I only use GitHub these days for open source stuff.
Your Job Suck?
Get a Better Job
Add Comment