The Average Learner 
Server Safety
So, I have my own personal VPS and a business VPS.
I spent a lot of time tinkering the VPSs in the past few weeks.
I’ve learnt a lot more about server safety and accessibility. Now, I only use tailscale to access my own services. My public facing websites are all proxied by Cloudflare DNS or Cloudflare Tunnel. So the public can never directly access my VPS.
I also separated two VPS for two distinct usage. Not just for the sake of task separation but also being future scaling aware. I can vertically and horizontally scale my business VPS (which only serves customer facing sites and apis) easily. And it won’t affects my personal services.
3-2-1 Backup
Rclone is favorable. I’ve digging it in the past year for different tasks. But now, I use it on my VPS to back up storage files, encrypt them, to Cloudflare R2 as an offsite backup, even though I have auto snapshots on Hetzner. From time to time, I will do the same for downloading all that to my USB stick for now, unless the storage grows way bigger.
Directus CMS
Yes, I’m back at it again. I guess I just connect with Directus.
How This Site Was Built - Obsidian
This site is built on top of Astro, it uses simple markdown files. I made quite some effort to make it work with Obsidian. So, as we speak, I’m typing this feed section in my Obsidian. I use Base to filter and sort my drafts and published posts. I also managed to make the image compression plugin in Obsidian where you drop in image it transfer to webp, all working in static build for Astro. (That wasn’t easy as I have to write logics to rename the files where you import, export, dev, all appears with different url)
I did also write a script to build, export them to /out/, then, wrangler deploy the folder on Cloudflare. So no one except me can access my codebase.
Why Am I Migrating to Directus
I’m going to migrate to directus, as my final CMS. I thought owning markdown is great. But in the end of the day, it’s about storage and convenience. As my article and assets grows, it is harder to manage and store the files. If I offload all that images on the cloud, it’s actually not a bad idea. My codebase for the site is cleaner without the content folder bloat.
And when I’m switching my frontend site, I don’t need to tackle the ../assets/images difference in these static site builder anymore.
Conclusion
I only wanted static generation for the best SEO possible, and also the low to none bandwidth traffic cost. And a clean workspace, for both the codebase to design my website, and the content writing experience.
Time to run that .sh script again to deploy this to Cloudflare.