6 ms·
If you truly wish to avoid this kind of problems you should think about hosting your own platform rather than jumping to the next one. Just because the smaller
by Hamcha 6y ago
If you truly wish to avoid this kind of problems you should think about hosting your own platform rather than jumping to the next one. Just because the smaller players haven't done anything bad doesn't mean they wouldn't.
Gitea/Gitlab are crazy easy to set-up nowadays, especially with a fully working CI/CD setup (I use Gitea+Drone and I love it, Gitlab comes with its own)
- deleted 6y ago[deleted]
- varispeed 6y agoYou are essentially shifting the problem from entity to entity and from one domain to another. If you self host your repository, your hosting provider can pull the plug and you essentially end up in square one. If you decide to self host, you should consider multi-cloud cross continent and cross political doctrine cluster.
- Silhouette 6y agoIf you self host your repository, your hosting provider can pull the plug If you self-host your repository, you don't have a hosting provider. There is no-one to "pull the plug" on the server at my business's office except the people who work in the building who could literally pull the plug, and I suppose the electricity and phone companies and our ISP. What you are talking about isn't self-hosting, it's hosting in the cloud on VMs you're renting directly. This is an intermediate step between self-hosting and using a fully hosted service like GitHub. With cloud-hosting, you are probably still subject to the whims of your hosting service. For example, you might be subject to occasional forced restarts of a long-lived instance if your hosting service needs to restart or replace the underlying physical server. However, in most cases, unless you're doing something illegal using their equipment or compromising their system in some way, these hosting services don't much care what you're running on your virtual box. This option is still far less risky than using a fully-hosted service, not least because you retain full control over the underlying data so there is almost nothing that can happen because of your hosting provider that a reasonable backup strategy can't fix within a relatively short amount of time.
- R0b0t1 6y agoYour ISP could refuse service. This has happened. If you manage to start an ISP people could refuse to peer.
- parliament32 6y agoIf you run your own AS you can buy bandwidth from literally any carrier, they famously don't give a triangular shit about what you do.
- naavis 6y agoWhat is AS?
- parliament32 6y agohttps://en.wikipedia.org/wiki/Autonomous_system_(Internet) https://en.wikipedia.org/wiki/Autonomous_system_(Internet)
- mynegation 6y agohttps://en.m.wikipedia.org/wiki/Autonomous_system_(Internet) https://en.m.wikipedia.org/wiki/Autonomous_system_(Internet)
- korethr 6y agoYes, but be honest, how many people can easily get their own AS? The barriers to getting an AS number are by design higher than the barriers to getting hosting with a random provider. If I can prove I have hundreds of hosts I want to connect to the Internet, I can probably successfully get an AS number and get in line for a slice IPv4 space when one becomes available. Joe Random probably can't.
- Silhouette 6y agoI think my other comment at https://news.ycombinator.com/item?id=23834351 https://news.ycombinator.com/item?id=23834351 applies here as well.
- PinguTS 6y agoMoving your own self-hosted stuff around different hosting providers is easy and doesn't interrupt the service, at least not for long. Just open an account at a new hosting provider. Fire up, your backup, changing DNS and you are up and running.
- jlokier 6y agoThis is great until your DNS account is blocked at the registrar for similarly opaque reasons.
- hundchenkatze 6y agoCouldn't you just switch registrars?
- jlokier 6y agoIt can be difficult if the old registrar won't cooperate. Especially if you registered under a pseudonym, as then you can't prove legal ownership of the domain either. But even if you register under your real name, you may need a court case to compel transfer if the old registrar won't cooperate.
- Silhouette 6y agoAt some point, there are risks you can't realistically control. There will always be extremely unlikely but theoretically possible catastrophic outcomes. Working DNS is great until global thermonuclear war or a supervolcano erupting renders the Internet rather irrelevant, for example. A sensible policy is to look at the risks you can do something about, try to assess how likely each threat is and what damage it would cause if it actually happened, and then make your plans taking into account how much you want to control those risks and what it costs you to do so. On this scale, something like the total collapse of law and order or the failure of the core infrastructure of the modern Internet and its governance processes is obviously less likely than one commercial service provider pulling the plug on unspecified or unreasonable grounds.
- kps 6y agoYou don't need a hosting provider. Your code fits on each developers' machine. (Remember when git was touted as a distributed version control system?) If it doesn't, you're at the scale where you're not worrying about your hosting provider dropping you — they're worried about you dropping them.
- jedieaston 6y agoThat's just as true of GitHub though, and isn't the problem. The problem is the related services, like issues, PRs and now CI/CD which all sit with the code but don't come down on a clone. That problem still hasn't been solved, which could mean your whole knowledge base goes missing if you lose access to the server. CI/CD can maybe be replicated from what's on your laptop, but if you don't have the PR history it could spell doom for big codebases that don't use extended commit messages a lot.
- ncmncm 6y agoI never understood why all that stuff wasn't also committed to the same repository. History is history, whether it's source code or talk about source code. Of course it could also be in a database thingy for querying and stuff. Some people say it is because Github wants to lock you in. I don't really believe that, but I am equally sure they don't mind if you lock yourself in.
- wiml 6y agoYou could use something like Fossil[1]. Or you could take regular backups of your project, which you should perhaps be doing anyway. [1] https://fossil-scm.org/home/doc/trunk/www/index.wiki https://fossil-scm.org/home/doc/trunk/www/index.wiki
- luckylion 6y ago> If you self host your repository, your hosting provider can pull the plug and you essentially end up in square one. Yeah, but it's much, much, much less likely than some script at GitHub getting triggered and shutting your account down. And even the cheap hosting providers do have ultra-premium-platinum-support compared to Google, GitHub, Amazon etc.
- MattGaiser 6y ago> And even the cheap hosting providers do have ultra-premium-platinum-support It is an odd thing to think that GoDaddy may have more merit as a solution than Github for hosting code...
- awakener62 6y agoI've had to resort to this I have 2 CentOS servers at the office. One running Gitlab CE the other running Gitlab Runner. We can't risk getting burned by Github or Gitlab if we forget to use the correct words in repos. Switching domain registrar and re-routing DNS is a simple and cheap thing if it ever becomes necessary.
- threatofrain 6y agoCan I have a single company act as the aggregator of all these technical abilities and package it into a single software product? :D
- sreevisakh 6y agoThere are two things you should ensure while self-hosting: 1. Always have independent and automatic data backup. A storage medium attached to a raspberry pi is plenty enough 2. Always choose a setup that you can deploy and migrate trivially It wouldn't matter what the hosting provider does if you have the power to pack up your bags and move elsewhere when they misbehave.
- shash7 6y agoProblem is that there are so many services that integrate with github directly that moving to other alternatives will also require moving/replacing those 3rd party services.
- ghostbrainalpha 6y agoIs it possible to self host the code, but then automate syncing backups to public Github. That way you can use 3rd party integrations, and be part of the Github ecosystem 99% of the time, but when they do something like this, you have an emergency place to work from?
- fennecfoxen 6y agoEmbrace, extend.