3 ms·

I blog on my own site, on my own domain name, on my own hardware. But it seems that most HN'ers use a static site generator and push to Github Pages. EDIT: mi

I blog on my own site, on my own domain name, on my own hardware. But it seems that most HN'ers use a static site generator and push to Github Pages. EDIT: might as well give the link: https://theandrewbailey.com/ https://theandrewbailey.com/

night-rider 4y ago
One caveat to GH Pages is if the repo’s public then all your amendments, typos, mistakes etc can be seen in a diff due to the way GitHub works. Not sure about private repos however. You may be able to conceal mistakes with that but not sure
- aurbano 4y ago
  I'd bet a significant amount of money that in most cases no one will ever bother to look through the commit history...
  - bombcar 4y ago
    And if you're really worried about it you do your work in one repo and "publish" to another.
    - azangru 4y ago
      Or git commit --amend and force-push :-)
- dont__panic 4y ago
  If you're publishing a site to the internet anyway, anyone could download every page on your site, submit it to archive.org, take a screenshot, or manually copy your posts onto a notepad. I find the GH Pages + Jekyll workflow works really well for my purposes, and it's been a nice way to play around with static site generation to boot.
whiskey14 4y ago
Nice set up and I'd like to run my own hardware if I had the time. One thing that has always put me off about running my own hardware is that someone in my house accidentally turns it off or we have a power outage. Do you have any tips for running your own hardware?
- theandrewbailey 4y ago
  I have it set up in my basement next to the router; both are plugged into a UPS. UPS claims to run for about 2 hours on battery (with an ear-piercing beep every minute the whole time), so it'll cover most momentary power outages. Admittedly, I got the UPS because I have the drives encrypted and didn't want to re-type the key every time I had a half second power outage. Oh, and backups. I'm pretty solid on backing up the data and server software (I think), but I don't have spare hardware, so if something physically breaks, I'll be down for a week or so.

night-rider 4y ago

One caveat to GH Pages is if the repo’s public then all your amendments, typos, mistakes etc can be seen in a diff due to the way GitHub works. Not sure about private repos however. You may be able to conceal mistakes with that but not sure

aurbano 4y ago
I'd bet a significant amount of money that in most cases no one will ever bother to look through the commit history...
- bombcar 4y ago
  And if you're really worried about it you do your work in one repo and "publish" to another.
  - azangru 4y ago
    Or git commit --amend and force-push :-)
dont__panic 4y ago
If you're publishing a site to the internet anyway, anyone could download every page on your site, submit it to archive.org, take a screenshot, or manually copy your posts onto a notepad. I find the GH Pages + Jekyll workflow works really well for my purposes, and it's been a nice way to play around with static site generation to boot.

whiskey14 4y ago

Nice set up and I'd like to run my own hardware if I had the time. One thing that has always put me off about running my own hardware is that someone in my house accidentally turns it off or we have a power outage. Do you have any tips for running your own hardware?

theandrewbailey 4y ago
I have it set up in my basement next to the router; both are plugged into a UPS. UPS claims to run for about 2 hours on battery (with an ear-piercing beep every minute the whole time), so it'll cover most momentary power outages. Admittedly, I got the UPS because I have the drives encrypted and didn't want to re-type the key every time I had a half second power outage. Oh, and backups. I'm pretty solid on backing up the data and server software (I think), but I don't have spare hardware, so if something physically breaks, I'll be down for a week or so.