Live data from Hacker News

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

ingau.me

121–130 of 248 posts

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

#121
post #54

Earlier quoted context omitted.

I’m using “fully owned” more in the sense of control rather than infrastructure ownership. The content lives locally, it’s versioned in Git, and everything’s built with open tools. I can move it to another host any time without being locked into a specific platform or format. I agree it’s not “self-hosted”. But compared to a closed CMS or paid platform, it feels meaningfully more in my hands.

In that sense, everything is "fully owned" and the phrase is meaningless. But in the context of the summary where you're using it, it certainly sounds like you are claiming ownership on the infrastructure

[deleted]

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

#122
I've been wondering how to get off the Zuckerverse (I still post on Instagram) and wondered if I can streamline uploading pictures to my own website. I imagine a Telegram bot that receives an image + caption, with backend code that creates such a blog post and does a git push is one way of doing it.

It seems this post talks about blogging from the desktop. But I just installed Obsidian on Android, it allows a filesystem vault. I think pairing it with Syncthing and some automation on my NAS (to do a git push to Github/Gitlab) could make it very streamlined.

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

#123
I had a near identical approach for my blog but I recently moved to a headless CMS. The bugbear being that it wasn't easy to publish if I wasn't at my desktop. With a headless CMS, I auth through Github via my phone, which also serves as the draft/publish step since posts in the CMS manifest as pull requests. It's been working great so far, with the caveat that the writing experience isn't as nice as Obsidian.

FWIW the CMS is Decap CMS and I have it configured likewise with Cloudflare Pages (since Pages supports functions that are needed for the auth/callback cycle).

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

#124
post #54

Earlier quoted context omitted.

I’m using “fully owned” more in the sense of control rather than infrastructure ownership. The content lives locally, it’s versioned in Git, and everything’s built with open tools. I can move it to another host any time without being locked into a specific platform or format. I agree it’s not “self-hosted”. But compared to a closed CMS or paid platform, it feels meaningfully more in my hands.

In that sense, everything is "fully owned" and the phrase is meaningless. But in the context of the summary where you're using it, it certainly sounds like you are claiming ownership on the infrastructure

The phrase to use would be something like data ownership. Something more specific.

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

#125

I've been wondering how to get off the Zuckerverse (I still post on Instagram) and wondered if I can streamline uploading pictures to my own website. I imagine a Telegram bot that receives an image + caption, with backend code that creates such a blog post and does a git push is one way of doing it. It seems this post talks about blogging from the desktop. But I just installed Obsidian on Android, it allows a filesys…

You can install or use any of the open pixelfed instances instead of Instagram.

I stopped uploading to Instagram the day they started using images for AI training.

If any of the file syncing applications work directly on the filesystem, I think you can use Obsidian on these folders and it'll sync automatically. On iOS, Obsidian defaults to iCloud, for example.

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

#126
post #54

Earlier quoted context omitted.

I’m using “fully owned” more in the sense of control rather than infrastructure ownership. The content lives locally, it’s versioned in Git, and everything’s built with open tools. I can move it to another host any time without being locked into a specific platform or format. I agree it’s not “self-hosted”. But compared to a closed CMS or paid platform, it feels meaningfully more in my hands.

In that sense, everything is "fully owned" and the phrase is meaningless. But in the context of the summary where you're using it, it certainly sounds like you are claiming ownership on the infrastructure

You don't own for example the comments in this platform or the post that you make on Facebook or writing platforms like substack, if you are using notion you don't your notes

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

#127
post #103

I have a sort of similar setup but I haven't started using Obsidian yet, it's on my todo list. I use Eleventy instead of Hugo, with its simple Eleventy-Base-Blog starter template. I use Github action to publish to Github pages instead of using Cloudflare. It's a nascent site/blog, haven't written much, no images yet, so I don't see the need for something more than Github pages right now. One thing I don't see the aut…

Nice setup. Yeah, I do commit drafts. My repo’s private, so I don’t mind keeping everything versioned there, including posts still marked as draft: true.

ah yes, I was going to mention that if it's private then it's not an issue.

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

#130

Earlier quoted context omitted.

In that sense, everything is "fully owned" and the phrase is meaningless. But in the context of the summary where you're using it, it certainly sounds like you are claiming ownership on the infrastructure

I do agree that the phrasing may be poor, but I see where ingav is coming from, if you're using hosted Wordpress and only keep your data in the Wordpress CMS, if Wordpress disappears today, so does all of your content. Although, that may seem foolish to some of us, there are definitely people out there who do that.

Yup. I'm using Vim + Hugo + GitHub + Netlify in a similar fashion. Just edit my markdown post, git push and it shows up on my website. I used some other static hosting service previously, don't even remember which one, but switching was super easy as I just pointed the output to some other bucket. So the public web hosting provider is completely commoditized and easy to switch from.

Also, I like treating my blog as a version-controlled, declarative "codebase" that's just a bunch of plaintext files (no MySQL tables, XML or JSON to crawl through).

Post reply on HN