4 ms·

This indirectly outlines one of the primary reasons organizations (like mine) prefer using GitHub Enterprise - we get the collaboration benefits of GitHub, but

This indirectly outlines one of the primary reasons organizations (like mine) prefer using GitHub Enterprise - we get the collaboration benefits of GitHub, but our data is entirely controlled and hosted by us. It's extra work and more costly overall, but it's a small price to pay for the data security.

ckdarby 3y ago
From my perspective, the upkeep of maintaining such versions is far from trivial. It involves dedicated resources ensuring the regularity and reliability of backups. Furthermore, it's rare to find organizations conducting comprehensive disaster recovery (DR) restorations of their self-hosted GitLab or GitHub instances. This is typically due to an inherent expectation that each upgrade will proceed without hitches and yield flawless operation. Moreover, the process of securing approval for NAT inbound rules, particularly for integrations with services like Jira, Slack and so on, often turns into a labyrinthine ordeal. It usually involves navigating the differing viewpoints and interpretations across multiple departments, each with its own unique stance, which further exacerbates the complexity of the task.
- yetanotherloss 3y ago
  As an aside, it remains funny to me how much effort organizations put into fighting NAT in 2023 instead of effort to just use ipv6. Of course then there is the embarrassment of azure ipv6 so it's perhaps somewhat forgivable:)
  - awesometech 3y ago
    There are many valid reasons to not use IPv6, it would make an interesting HN article.
    - Fogest 3y ago
      My ISP still doesn't even support ipv6. From my limited understanding that itself would already make it a problem to access an ipv6 only site.
smcleod 3y ago
I think you mean GitHub Enterprise Server. GitHub Enterprise is still a cloud / SaaS product.
- ec109685 3y ago
  Enterprise, even cloud hosted, would prevent things like a fork being public.

ckdarby 3y ago

From my perspective, the upkeep of maintaining such versions is far from trivial. It involves dedicated resources ensuring the regularity and reliability of backups. Furthermore, it's rare to find organizations conducting comprehensive disaster recovery (DR) restorations of their self-hosted GitLab or GitHub instances. This is typically due to an inherent expectation that each upgrade will proceed without hitches and yield flawless operation. Moreover, the process of securing approval for NAT inbound rules, particularly for integrations with services like Jira, Slack and so on, often turns into a labyrinthine ordeal. It usually involves navigating the differing viewpoints and interpretations across multiple departments, each with its own unique stance, which further exacerbates the complexity of the task.

yetanotherloss 3y ago
As an aside, it remains funny to me how much effort organizations put into fighting NAT in 2023 instead of effort to just use ipv6. Of course then there is the embarrassment of azure ipv6 so it's perhaps somewhat forgivable:)
- awesometech 3y ago
  There are many valid reasons to not use IPv6, it would make an interesting HN article.
  - Fogest 3y ago
    My ISP still doesn't even support ipv6. From my limited understanding that itself would already make it a problem to access an ipv6 only site.

smcleod 3y ago

I think you mean GitHub Enterprise Server. GitHub Enterprise is still a cloud / SaaS product.

ec109685 3y ago
Enterprise, even cloud hosted, would prevent things like a fork being public.