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.
How I blog with Obsidian, Hugo, GitHub, and Cloudflare
141–150 of 248 posts
Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare
#142[stub for offtopicness] [submitted title was "How I Blog with Obsidian, Hugo, GitHub, and Cloudflare – Zero Cost, Fully Owned"]
Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare
#143Ps: Folks should chill out about wording here and there.
Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare
#144Droobox and similar services have never been seamless for me with Obsidian. There will inevitably be some conflict when the same file gets edited on two machines, and an ugly conflict file will appear, with no easy way to resolve it without a specialized diff tool. Sometimes this conflict file will get unnoticed and a change will fall theough the cracks. Not a deal breaker - but not "seamless" either.
Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare
#145Earlier quoted context omitted.
What do you mean "fully owned"? There is no mention of that in the post Edit: I guess you mean the content itself is still on your machine if the services go away, and you can choose to host them elsewhere
I don't think there is a good term in the context of the Internet. Or offline for that matter. Even if you printed your blog and handed it out on street corners, for it to be "fully owned" would that mean you make your own ink and paper?
Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare
#146Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare
#147Earlier 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.
You're getting a lot of pushback but I agree with the sentiment of fully owned. Sure, the git repo and static files are hosted elsewhere for now. But you can easily switch that place any time. Meanwhile all the important stuff: the post data, the code to format them, the domain name, the process itself. That's all in your complete ownership and control. It's a very different bargain than, say, hosting things at wordp…
Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare
#148Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare
#149> notes sync seamlessly across devices Droobox and similar services have never been seamless for me with Obsidian. There will inevitably be some conflict when the same file gets edited on two machines, and an ugly conflict file will appear, with no easy way to resolve it without a specialized diff tool. Sometimes this conflict file will get unnoticed and a change will fall theough the cracks. Not a deal breaker - but…
- you haven't setup auto save/auto sync
- multiple people editing the documents
- you frequently have no Internet and the application closed when you re-gain Internet or similar
if only a single person edits the same document at a time and you always sync changes when they happen that should be a non issue
Re: How I blog with Obsidian, Hugo, GitHub, and Cloudflare
#150This is really good to help overcome many fears of blogging!! Once you know your obsidian is linked, all your notes and writing would take next level of drafting to actually becoming a post. Thank you ingav! Ps: Folks should chill out about wording here and there.