GitHub Workflows & Actions
The next learning goal for today and tomorrow: automating continuous integration (CI) and continuous delivery (CD) using GitHub's workflows and actions, written in yml files. Yes, this is a completely different scripting language. Yes, I am quite possibly even more insane than I normally give myself credit for most of the time. But someone's gotta do it, right?
I now understand the very basic concepts, the kinds of things possible, and how to get the most out of the next 2 days or so with this learning. Essentially all tasks that can be automated once code has been pushed to the repo will be setup before the first MOOVPAD static site is released. And this automation, along with that for the server-side base system, will serve as initial templates for future projects. So in theory, MOOVPAD can be releasing updates for each app, webAPI, and even the base system, and do so multiple times daily if necessary.
My goal: once code is written and uploaded, it gets tested, scanned for safety/security, and uploaded to the right places... all kinda abra-cadabra automagically like 🙂
Stay awesome,
EMH
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.