91–100 of 248 posts
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.
Earlier quoted context omitted.
Not “fully-owned” though if you need external services to do the heavy lifting. I think they mean deployed onto a personal vps.
I'd argue it is, because it's portable to any other service. As in you own all the content and methods to generate it.
Earlier quoted context omitted.
I really dont agree with "fully owned", you arent running on anything you actually own ie self-hosting. It's all on the cloud , which dont get me wrong, is pretty cool and helpful, but hardly yours.
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.
I think blogs should be built like this to make preservation easier. I'd love to have something that make content domain agnostic, more like git that allows cloning and distributing content without forcing people to guess when to pull and archive if they want to keep track of things.
One thing I don't see the author mention that is part of what I plan to do with Obsidian is use Syncthing (which I already use for other things) so I can work on a post when I'm not at my laptop. Probably just to write down ideas/notes and then fully work it out when I get to my laptop.
If the blog author is here, curious if they commit drafts to their repo or not. I personally don't commit drafts. Besides also using 'draft: true` in the front-matter, I gitignore any markdown file where the filename starts with the word "draft". When I'm ready to publish I rename the file.
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.
I see, I do agree it is nice to have your data fully owned (like really) and safe on device (or devices), though, sometimes it doesnt feel like enough in the ever changing landscape of the internet.
Anyway, the important thing is being in control of your own data. With proper off-site backups and reproducible setups using containers, migrating between VPS providers should usually take just a few hours.
I fully understand the arguments for (and against) managing your own server. But I've not been convinced by any arguments for that server being in your house/office rather than a climate controlled warehouse somewhere.
Well, unless you enjoy setting up and managing the physical hardware yourself of course. That's fully reason enough.
The Hugo/GitHub combo has been around/mentioned for some years.. I thought of running a blog once (but then.. no) and this was the choice I would have made. But on the other hand, if you are going to post something online, just go to blogspot and call it a day. Because that's what you did there. A blogspot (but on MS instead of Google) with many-many-many extra steps.
Earlier quoted context omitted.
Not “fully-owned” though if you need external services to do the heavy lifting. I think they mean deployed onto a personal vps.
"Fully-owned" when it's relying on GitHub Pages, Hugo, Obsidian and Cloudflare to function. Two of which are services operated by a corporate entity and one of which is a closed source piece of software. The only thing "owned" here is the fact that the entire blog is simple markdown and the domain name. However, that doesn't mean it's very portable. It's not impossible, but it's a lot more work than I would want to d…
I'm curious about the pros and cons of Cloudflare pages versus GitHub pages. Given that you're using GH as a repo, would it be simpler to also use it to serve pages?
https://docs.github.com/en/pages/getting-started-with-github... > GitHub Pages is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). Not finding a similar mention for Cloudflare... commercial sites are fine…
Curious though how it handles a surge in requests, like from being on the front-page of HN. But many open source projects host their doc pages with Github pages and some of those get a lot of traffic so I'm sure that it's not an issue