131–140 of 248 posts
Earlier quoted context omitted.
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.
But he doesn’t. If Cf or Gh go down he has to reconfigure the whole mess. Portability != full-ownership.
Honestly this sounds a bit cumbersome. I built my blog years ago using Puput ( https://github.com/APSL/puput ) and Render, and it has been running strong with minimal maintenance since then, with hundreds of posts. The software is all open source and free other than the minimal hosting fees. If I want to do a post, I log in, draft the post in a simple rich-text editor with image support and keyboard shortcuts for for…
Totally get that. My post was meant as a way , not the way . I already use Obsidian for most of my writing and notes, so this setup just fits naturally into my workflow.
Keeping Hugo installed and up to date as part of the publish process seems like a headache as well. I like the blog to be totally separate from my local machine, so if I change anything or switch laptops, it doesn't interfere with the publication process.
Manually adding the Hugo front matter to each post also strikes me as annoyingly fiddly, although you could use a text expander app to handle most of it. Another issue is that I'm not sure that Markdown would do well for the full scope of formatting, such as aligning images and adding image captions.
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.
Earlier 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?
Earlier quoted context omitted.
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.
People get protective of the term self hosted, but all I know is that if I search "how to self host" for any open source project, 90% of the guides at least , probably including the project's own docs, will be about installing on a VPS. 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…
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.
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.
But if they kill your access to those accounts do you have a method to force them to let you back in to get “your” content? Serious question as I self-publish and use a distribution service for my music but I stop short of your claim. I’m an independent rights holder. I don’t own the platforms upon which I choose to distribute my work - terminology does matter and, well, you’re claiming something basically untrue bec…
I have a very similar setup, but I went a step further by writing a custom Obsidian plugin that handles compressing assets / transforming frontmatter / pushing the bundle up to my Github blog repo. Github has an automated action that then uses Pelican (a python based static site generator) to convert to HTML and deploys it to my VPS where it is served by Caddy. Makes it very easy to have a WYSIWYG interface, the blog…
Nice! I especially like the automatic compression of assets. It's such a pain to do it manually that I don't bother most of the time. I cross my fingers and hope the reader has a fast internet connection.
I really wanted to use animated WebP but the iOS decoding is SUPER unreliable often resulting in choppy inconsistent framerates.
One thing I don't do but I know is more common is using elements to serve scaled assets depending on if the user is coming from mobile vs desktop.
Depending on what you use for your blog, you might look and see if the SSG has plugins for media optimization. By the time I figured that out, I had already handrolled my own. :p
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
What if it's a dedicated machine, colocated? What if it's at home, but I pay an ISP?
edit: Downvoted, care to explain why? I genuinely wrestle with this question. I self-host lots of services at home - and I also self-host services on a cloud VPS, which have better availability and security posture with regards to my home network for things I make public or semi-public. Some have told me this isn't "self-hosting" and I am not sure where the line is drawn.
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
The only thing I want is to implement a gui for adding and editing posts.