🏳️‍⚧️ and I make good posts sometimes!

pfp by me!
banner by https://twitter.com/spect_ion


fediverse
‪@PolyWolf@social.treehouse.systems‬
bluesky
@wolf.girl.technology

now that Astro has their Content Layer API coming in their next major release, I'm suddenly a lot more flexible in how I can host the markdown files that power my blog, no longer limited to just "checked in to the Git repo". To go along with a time-honored tradition, let's make a table!

GitS3SQLiteThird-party CMS
Backup-abilityVery, almost requiredManually, tied to provider's CLIManually, w/ scp?
Snapshot-abilityVery, requiredSomewhat, potentially automatic, but probably not going toSomewhat, probably manual, but probably not going toProbably Not
Astro Load-abilityEasyPotentially easyPotentially hardEasy if supported, potentially hard if not
Use My Own Post ComposerYesYesYesNo, but maybe that's better?
Editable w/o Post ComposerYesNot EasilyEven Less EasilyLikely No
Ease Of Post Composer PostingVeryPrettySort OfVery
Ease Of Post Composer EditingNot VeryPrettySort OfVery
Deployment Solution?Already BuiltNot BuiltNot BuiltNot Built
Supports Drafts?NoYesYesProbably
Also Stores Media?Yes, but it shouldn'tYesNoProbably?
CategoryGitS3SQLiteThird-party CMS

yep, as expected, making a table was very helpful! it really seems like Git is still the best solution, followed by S3 as a close second. Doing more research, it seems like "Git-based CMS" is a not-uncommon thing, so really I'm pretty good where I am already.

The biggest thing I might change is moving the image files out of my Git repository. It makes clones take a lot longer than needed, right now they're actually the largest part of redeploys. I think having them be hosted from a S3 + Cloudflare combination & using Astro's Remote Image Functionality will help speed up build times, because that should be faster than pulling them thru Git. idk tho we'll see.


You must log in to comment.

in reply to @PolyWolf's post: