Ask HN: Self-host a blog securely – how? (WP? Staticgen?)
I'd like to self-host it, but sometimes the part of the drive that enables creativity contradicts / is interfered with by the part of the brain that is required for technical planning, even something as minor as a tech blog setup.
At least for me.
I'm thinking I host a WordPress instance privately, at home, and I use a staticgen system (Pelican??) to export and push that out to a STATIC public site on a VPS I control. It still feels like a lot of work though.
I'm a systems guy and I'd like the WYSIWYG-type platform on which I can focus on ideas and post my blog without worrying about security, hosting, etc. And it needs to be at least somewhat pretty, with a discus or other commentary plugin at the bottom and ability to show pretty screenshots.
Has anyone experimented with Wordpress -> Pelican or is there something better?
If I spend too much time hacking away at edge conditions, then that's less time I get for creativity.
Any ideas would be appreciated.
If you want to host site on S3 you can use the fork of Simply Static https://github.com/kennu/simply-static-s3
This is faster than having to learn Pelican and even those other systems which might also be great, but a bit heavy weight for my purposes.
Thank you, this might be the solution I was looking for.
What is the purpose of this exercise? Blogging or learning WP->static page migration path? If your purpose is blogging and you have no interest in admin and revenue generation, just host on WordPress.com. If you want more flexibility, just self-host WordPress.
Why make it more complicated by adding another path of WP->Static Pages?
WordPress can pretty insecure if not micromanaged. It's often a vector for hacks, and requires meticulous updating.
https://www.wordfence.com/blog/2016/03/attackers-gain-access...
You don't even need to run a VPS, although if you do so you can set up a nice publication pipeline with Git. But you can equally just throw the static content up on S3 or Google Cloud Storage, optionally with a CDN in front of it.
You can also run your blog on Gitlab if you feel inclined: they have a CI process meaning that when you commit new source content to your git repo, it'll automatically get built and appear on your site. I found the domain support a little flaky there when I tried it, but apparently they've updated their setup since then.
Simply put your file in an S3 bucket and point the name server.
If you need a httpS connection (and I needed to take payments) simply use cloudfront and you are set.
They also have very recently released new themes.