4 ms·

It takes like fifteen minutes to set things up. Every startup needs a competent Unix sysadmin. EDIT: a Threadripper will do for CI. Quick as you like.

deleted 4y ago
[deleted]
anonymousab 4y ago
GitHub is far, far more than just a git repo. Issue tracking, project boards, commit status systems/check systems, deployment tracking and monitoring, fully fledged CI and deployment pipelines (actions/workflows) written in their own flavor, etc. All sorts of webhooks, complex arrangements of teams and access controls, cross repo, cross,-org and cross enterprise account linkages. Large object storages, container registries, and package repositories. And of course, the existing context of all this stuff; setting up an alternative != completely migrating and validating everything from the original. Replacing all that with something as scalable, flexible and agreeable with potentially thousands of global developers is far more than '15 minutes' of work. Several orders of magnitude more. Even on the git repo question alone, if you're an enterprise of some size, you'll have hundreds or maybe thousands of repos that could be potentially gigabytes in size (for any one repo) for code alone. Moving to a self hosted solution requires far more than just throwing some threadrippers and enterprise drives at the problem. And that's assuming the best outcomes. A competent UNIX sysadmin would be the one yelling not to throw the baby out with the bathwater here, because they would know just how hard this stuff is at scale.
- noasaservice 4y ago
  Again, a Linux/Unix admin is worth their weight in gold-press latinum. Pop in a self-hosted GitLab install, configure SAML or AD auth for SSO. It's all GIT so importing all commits (and not losing history) isn't hard - just tedious. For testing pipeline, use Selenium on a 32 core threadripper running linux, with 1/4 TB ram. You can get upwards of 400 headless chromes on that. Throw in NodeRed for overall process automation (think: tying in disparate APIs with a low code environment). I've done this, with exclusion of the selenium checks themselves (there was a qa team for that), in like 2 weeks.
  - rsstack 4y ago
    150 lbs of gold-pressed latinum costs a lot more than GitHub Enterprise, and for a marginal improvement in uptime. And you need 3 of them if you want on-call, which you should if you're trying to beat GitHub's availability.
  - anonymousab 4y ago
    It's literally not all git. Every single thing I mentioned outside of the git repository itself is not git, and makes up a significant amount of services that would require disparate, specific replacements and buy in and compatibility with all of the developers, teams and units of a company. It's a vast, extremely costly amount of work. Just throwing up a server somewhere running git and a few software packages is nowhere near the same thing.
    - bogwog 4y ago
      Gitlab has all those non-git features, and then some. Migrating to it from Github might not be easy, but it's definitely worth it IMO to invest in the product that gives you more options, instead of getting locked in to something like Github.
- exikyut 4y ago
  Some deployments might be able to leverage GitHub Enterprise, which is a $231/user/year GitHub-in-a-VM-image. It's pretty much the GH source code (running through a modified copy of Ruby so the on-disk .rb files are scrambled). https://github.com/pricing https://github.com/pricing https://docs.github.com/en/enterprise-server@3.2/admin https://docs.github.com/en/enterprise-server@3.2/admin Active/passive HA is possible: https://docs.github.com/en/enterprise-server@3.2/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica https://docs.github.com/en/enterprise-server@3.2/admin/enter...

deleted 4y ago

[deleted]

anonymousab 4y ago

GitHub is far, far more than just a git repo. Issue tracking, project boards, commit status systems/check systems, deployment tracking and monitoring, fully fledged CI and deployment pipelines (actions/workflows) written in their own flavor, etc. All sorts of webhooks, complex arrangements of teams and access controls, cross repo, cross,-org and cross enterprise account linkages. Large object storages, container registries, and package repositories. And of course, the existing context of all this stuff; setting up an alternative != completely migrating and validating everything from the original. Replacing all that with something as scalable, flexible and agreeable with potentially thousands of global developers is far more than '15 minutes' of work. Several orders of magnitude more. Even on the git repo question alone, if you're an enterprise of some size, you'll have hundreds or maybe thousands of repos that could be potentially gigabytes in size (for any one repo) for code alone. Moving to a self hosted solution requires far more than just throwing some threadrippers and enterprise drives at the problem. And that's assuming the best outcomes. A competent UNIX sysadmin would be the one yelling not to throw the baby out with the bathwater here, because they would know just how hard this stuff is at scale.

noasaservice 4y ago
Again, a Linux/Unix admin is worth their weight in gold-press latinum. Pop in a self-hosted GitLab install, configure SAML or AD auth for SSO. It's all GIT so importing all commits (and not losing history) isn't hard - just tedious. For testing pipeline, use Selenium on a 32 core threadripper running linux, with 1/4 TB ram. You can get upwards of 400 headless chromes on that. Throw in NodeRed for overall process automation (think: tying in disparate APIs with a low code environment). I've done this, with exclusion of the selenium checks themselves (there was a qa team for that), in like 2 weeks.
- rsstack 4y ago
  150 lbs of gold-pressed latinum costs a lot more than GitHub Enterprise, and for a marginal improvement in uptime. And you need 3 of them if you want on-call, which you should if you're trying to beat GitHub's availability.
- anonymousab 4y ago
  It's literally not all git. Every single thing I mentioned outside of the git repository itself is not git, and makes up a significant amount of services that would require disparate, specific replacements and buy in and compatibility with all of the developers, teams and units of a company. It's a vast, extremely costly amount of work. Just throwing up a server somewhere running git and a few software packages is nowhere near the same thing.
  - bogwog 4y ago
    Gitlab has all those non-git features, and then some. Migrating to it from Github might not be easy, but it's definitely worth it IMO to invest in the product that gives you more options, instead of getting locked in to something like Github.
exikyut 4y ago
Some deployments might be able to leverage GitHub Enterprise, which is a $231/user/year GitHub-in-a-VM-image. It's pretty much the GH source code (running through a modified copy of Ruby so the on-disk .rb files are scrambled). https://github.com/pricing https://github.com/pricing https://docs.github.com/en/enterprise-server@3.2/admin https://docs.github.com/en/enterprise-server@3.2/admin Active/passive HA is possible: https://docs.github.com/en/enterprise-server@3.2/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica https://docs.github.com/en/enterprise-server@3.2/admin/enter...