Live data from Hacker News

How I blog with Obsidian, Hugo, GitHub, and Cloudflare

ingau.me

161–170 of 248 posts

Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare

#161

Great stuff, looking forward to your next blog post in 1 year: “How I rebuilt my blog on…” A fun hobby of mine is Googling “how I built this blog with [next.js/Gatsby/etc etc]” and going to page 10 of the Google results. It’s just hundreds of developer blogs with no blog posts other than the ones announcing how the blog was built.

I’ve noticed this a lot, too, and made this drawing as a joke: https://rakhim.org/honestly-undefined/19/

I'm in the "old-ass blogger.com site" category, with posts going back to '05.

Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare

#162

Great stuff, looking forward to your next blog post in 1 year: “How I rebuilt my blog on…” A fun hobby of mine is Googling “how I built this blog with [next.js/Gatsby/etc etc]” and going to page 10 of the Google results. It’s just hundreds of developer blogs with no blog posts other than the ones announcing how the blog was built.

Haha. I guess discovering & teaching how to do X is more rewarding than doing X. It applies to blogging, PKM and productivity too.

Is there a name for this phenomenon where this actually turns out to be true? Closest I can think of is "During a gold rush, sell shovels".

Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare

#163

Great stuff, looking forward to your next blog post in 1 year: “How I rebuilt my blog on…” A fun hobby of mine is Googling “how I built this blog with [next.js/Gatsby/etc etc]” and going to page 10 of the Google results. It’s just hundreds of developer blogs with no blog posts other than the ones announcing how the blog was built.

I started with and used Jekyll for almost ~10 years and ~500 posts before switching to Hugo.

I have a 7,000 word blog post on how and why I switched which I didn't publish yet because I wanted to wait 6+ months with Hugo to make sure I ironed out all of the kinks. I guess I'm the anti-case for this one! Maybe I should post this one next week. It's been quite stable.

Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare

#164

I feel like Obsidian Publish must be really doing something wrong, when this sort of thing keeps catching interest when it's a lot more effort than just paying $8/mo.

The one issue I have with Obsidian Publish is it's a bit of a pain to put your own SSL-secured domain in front of it. I run a nginx-based proxy as a bandage. I can see why someone would not want to pay $8/m for it though when there are a ton of free options out there. You have to remember that devs love flexing their skills and automating a blog can be fun, it's not really anything wrong with the service.

-Your own- yes, but Cloudflare is extremely easy.

Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare

#166

Great stuff, looking forward to your next blog post in 1 year: “How I rebuilt my blog on…” A fun hobby of mine is Googling “how I built this blog with [next.js/Gatsby/etc etc]” and going to page 10 of the Google results. It’s just hundreds of developer blogs with no blog posts other than the ones announcing how the blog was built.

or filler posts like this one in the same blog:

https://ingau.me/notes/asymmetric-encryption/

Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare

#167

    > This stack gives me full control: no subscriptions, no vendor lock-in,
    > and no risk of platforms disappearing or changing policies.
I'm not trying to dunk on the author, but this sentiment encapsulates a tremendous paradigm shift in the meaning of "full control", compared to say:

* Writing in obsidian

* Syncing files via git

* Publishing via nginx hosted on the cheapest possible vps (with https via let's encrypt)

Running a static blog is one of the easiest scenarios to self-host, because even if you get slashdotted, nginx should be able to handle all the requests even if you're host it on a potato

It's not free, but you can get a VPS for $20-$30 a year.

This isn't the best fit for everyone, but it seems weird to talk about "full control" and "no risk of platforms disappearing" when you're relying on the free tier of two external companies

Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare

#169

Very nice post! I do almost the same, but instead I use Astro. I use Obsidian, with a GitHub submodule for the content, and host it all as a static page. I wrote about that here if anyone is interested: https://bryanhogan.com/blog/obsidian-astro-submodule

Same. I even built this for my GF to use. You don’t even need to download vscode as you can run it in a free dev container in browser: https://github.com/easy-astro-blog-creator/easy-astro-blog-c... The only thing I want is to implement a gui for adding and editing posts.

What you built is actually so great! Was also thinking of building something that makes blogging for less technical people easy without the downsides of a walled system.

Haven't heard of dev containers like that before, but cool to see that they can be used like that.

Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare

#170

> This stack gives me full control: no subscriptions, no vendor lock-in, > and no risk of platforms disappearing or changing policies. I'm not trying to dunk on the author, but this sentiment encapsulates a tremendous paradigm shift in the meaning of "full control", compared to say: * Writing in obsidian * Syncing files via git * Publishing via nginx hosted on the cheapest possible vps (with https via let's encrypt)…

The point is that because of the way they structured their blog it would be trivial to do exactly this if they ever needed to. There's no complicated export from a locked in application, you just move your blog files from one host to another (maybe to your own VPS).

The overhead of switching from Cloudflare to a VPS if they needed to is really not that much larger than switching from one VPS to another, so they likely figured it wasn't worth paying $30/yr to own the whole stack, as long as they architected it such that they could own the whole stack if they needed to.

Post reply on HN