3 ms·

On the contrary. If it's on a git repo you have a copy of, it doesn't matter who's service is being used. Migration becomes trivial. This is probably the singl

On the contrary. If it's on a git repo you have a copy of, it doesn't matter who's service is being used. Migration becomes trivial. This is probably the single greatest upside of static site generators.

Andrew_nenakhov 5y ago
If you have a copy of it, you have a backup. Which is good, but not really groundbreaking. You still depend on the hosting provider who lets you keep your stuff on their servers.
- Karunamon 5y ago
  The internet is an interconnected series of "someone's service". Your definition is so broad as to be a meaningless tautology. I host my blog on web space that I pay for. If they stop hosting me, I move. This takes literally one line in a post commit hook to effect.
  - Andrew_nenakhov 5y ago
    the degree of using 'someone's service' when you host your own VPS on your own domain is quite a bit different from when you are using gitlab.
    - folkrav 5y ago
      Honestly, in the context of hosting a static site, how?
- theamk 5y ago
  You are always going to depend on someone - web host, or VPS host, or colo service, or ISP (if the server is in your house). Not to mention domain registrar. The webpage is "yours" as long as you are the one in control of content, can migrate anywhere else without users knowing, and third parties can only disable your site but not edit. Both github pages and machine in the basement satisfy that rule.
- lolinder 5y ago
  With a static site, the git repo is the main database and the stuff that's publicly accessible is the copy. I could seamlessly host it on three different providers at once (GitLab, Netlify, DigitalOcean) if I cared to, all mirroring my repo. I can't lose access to my repo unless GitLab decides to ban me and I simultaneously wipe my hard drive. This is very different from a typical VPS, where if I'm not conscientiously making backups my provider could pull the plug and wipe my data.

Andrew_nenakhov 5y ago

If you have a copy of it, you have a backup. Which is good, but not really groundbreaking. You still depend on the hosting provider who lets you keep your stuff on their servers.

Karunamon 5y ago
The internet is an interconnected series of "someone's service". Your definition is so broad as to be a meaningless tautology. I host my blog on web space that I pay for. If they stop hosting me, I move. This takes literally one line in a post commit hook to effect.
- Andrew_nenakhov 5y ago
  the degree of using 'someone's service' when you host your own VPS on your own domain is quite a bit different from when you are using gitlab.
  - folkrav 5y ago
    Honestly, in the context of hosting a static site, how?
theamk 5y ago
You are always going to depend on someone - web host, or VPS host, or colo service, or ISP (if the server is in your house). Not to mention domain registrar. The webpage is "yours" as long as you are the one in control of content, can migrate anywhere else without users knowing, and third parties can only disable your site but not edit. Both github pages and machine in the basement satisfy that rule.
lolinder 5y ago
With a static site, the git repo is the main database and the stuff that's publicly accessible is the copy. I could seamlessly host it on three different providers at once (GitLab, Netlify, DigitalOcean) if I cared to, all mirroring my repo. I can't lose access to my repo unless GitLab decides to ban me and I simultaneously wipe my hard drive. This is very different from a typical VPS, where if I'm not conscientiously making backups my provider could pull the plug and wipe my data.