7 ms·

That is terrible and a good reminder that using the "cloud" means that you don't really control your destiny. A quick googling around reveal a couple of option

That is terrible and a good reminder that using the "cloud" means that you don't really control your destiny. A quick googling around reveal a couple of options for backing up everything from github (but I'm not sure what you'd do with a backup if you got kicked out like the OP).

jarfil 7y ago
It's also a good reminder of why data portability is important. For the git part, you can just git push to another service, even a selfhosted one, and be up and running in no time, and GitHub does keep pages and wikis in git... but all the tickets, that's a problem, and why I don't trust GitHub to be a canonical source for development.
- est31 7y ago
  Gitlab has a feature to copy an entire Github repo including issues and issue threads, etc. You can also enable options for it to act as a mirror or to make GitHub act as the mirror for Gitlab. I'm not sure whether there is a mode to keep the issue threads synced as well without manual intervention. That'd be full data portability.
- raxxorrax 7y ago
  That is generally a good thing about cloud applications that you are forced to bundle everything. Most of the software I run on AWS could easily be transported to Google, Microsoft or some other service. Sure, there are exceptions and optimizations for specific services but overall it did increase portability of server applications quite a bit. Maybe the times were you just need that legacy windows 2000 server encapsulated with 7 firewalls and proxies are finally over. I usually prefer to host my stuff on private servers, but people unreasonably want to put as much software as possible into cloud providers. I think the reason for that is more often cocaine abuse and wanting to be hip instead of technical/financial arguments, but it is what it is.
chaz 7y ago
I think the reminder is just that backups are necessary, and cloud isn't a required condition. I had a bare-metal host turn off my server because they were concerned I was violating the trademark of a big company with what I was serving. That big company was my client and I had permission, but the host shot first and asked questions later (actually, I had to call them when I saw the site went down).

jarfil 7y ago

It's also a good reminder of why data portability is important. For the git part, you can just git push to another service, even a selfhosted one, and be up and running in no time, and GitHub does keep pages and wikis in git... but all the tickets, that's a problem, and why I don't trust GitHub to be a canonical source for development.

est31 7y ago
Gitlab has a feature to copy an entire Github repo including issues and issue threads, etc. You can also enable options for it to act as a mirror or to make GitHub act as the mirror for Gitlab. I'm not sure whether there is a mode to keep the issue threads synced as well without manual intervention. That'd be full data portability.
raxxorrax 7y ago
That is generally a good thing about cloud applications that you are forced to bundle everything. Most of the software I run on AWS could easily be transported to Google, Microsoft or some other service. Sure, there are exceptions and optimizations for specific services but overall it did increase portability of server applications quite a bit. Maybe the times were you just need that legacy windows 2000 server encapsulated with 7 firewalls and proxies are finally over. I usually prefer to host my stuff on private servers, but people unreasonably want to put as much software as possible into cloud providers. I think the reason for that is more often cocaine abuse and wanting to be hip instead of technical/financial arguments, but it is what it is.

chaz 7y ago

I think the reminder is just that backups are necessary, and cloud isn't a required condition. I had a bare-metal host turn off my server because they were concerned I was violating the trademark of a big company with what I was serving. That big company was my client and I had permission, but the host shot first and asked questions later (actually, I had to call them when I saw the site went down).