Building a deployment and management tool needs testing and refinement. But primarily a lot of testing. The best way to do that is to just run it in production and make sure it doesn't break.
The goal for this week is to at least run this site in production, managed by Strackt. The first part of that is to have it provisioned and managed with manually triggered deployments. The second step will be to trigger it fully through the frontend UI, after that, all triggers should also be automated. But first things first...
Step one has been implemented, now it's time to test, and the best test is with new content to deploy 😀 Right now it runs on a development server but in a couple of days it should move to a production server.
In parallel, I'm writing loads of feature, unit, and execution tests to better monitor all elements of the pipeline. For now, I'm also bolting on loads of external monitoring tools to see how the servers and the deployments perform.
Done
- Manually triggered end to end deploment 👇🏻🚀
Upcoming
- UI integrated deployment 🖱
