PostieDay 28 · 27 September 2026
Chapter 1 · 7 days to the chapter deadline
- Fix Problems with CMS Deployments
As much as I was surprised the CMS Migration from hosted to self-controlled infrastructure was pretty much done in 30 minutes at the time I had other commitments so couldn't test it properly. I went through things today writing my posts and it didn't deploy properly...
Not only did it not deploy but when I did it manually for some reason it then began spamming deployments every 30 seconds which didn't make sense. Turns out there was temporary deployment service timer daemon which deployed the old version when it detected a change running for the past 5 days?! It makes no sense as to why but it even proceeded the CMS migration itself which is even weirder.
I removed that service and then worked to figure out why things still weren't updating. I had updated the CMS URL in wrangler and double checked online but there were still issues... turns out the build variables which (for whatever reason) can't be defined or influenced from the wrangler file needed to also be updated...
Makes sense of course but you can spend a long time over complicating things and trying to figure out why something isn't working that you get kind of lost in the sauce as I did. To be fair I would've found it earlier but I thnk the weird deploy check user service daemon thing absolutely threw me through a loop. I mean why was that even a thing....
- Transfer Postie to it's Own Cloudflare Account
This is the thing that has been exciting and terrifying me in equal measure. I didn't want to do this migration because I knew it would be a slog but I knew I needed to do it sooner than later so I can actually continue development.
One of the things that actually finally made me bite the bullet and get to it was actually how smoothly the CMS migration went. What's clear is making sure that it has all of the API keys and specific wrangler access BEFORE starting.
For these massive undertakings I start with making my requirements clear and making the AI explore both the codebase and the two CF accounts and plotting out a plan of attack. (Not in plan mode of course - so 2025) and by working collaboratively I was able to get the plan to a state where i just said "implement it" and it did.
Admittedly this is because the project contained cloudflare / wrangler / skills and while this might be frontloading it a bit I feel like with this purely CF API that ok. It worked and now things are separated from my personal/business and Postie.
I even decided not to add back the other email addresses still on my CJRI account. I want to do this later when I fix the onboarding flow. For now I can use the gopostie emails without much issue.
This project is finally getting exciting again. Let's keep the ball rolling!