Why This Matters For MOOVPAD
There are obvious concerns for any cloud-based apps, and some perhaps less obvious ones. Server-side security and file system monitoring, access control and logging, as well as routine maintenance are among the obvious examples. But in the case of MOOVPAD apps, there's also the need to integrate all of these functions with the other management systems
The screenshot above shows some of the learning I've just completed regarding some of the more advanced elements of bash scripting. Of course I am still a noob at this stage, but thankfully, I've realised I can also be a good learner. So the principles covered in this tutorial will help guide me through further work to develop the server-side management tasks in ways that will link up well with the MOOVPAD management and monitoring systems that are also reporting on webAPI errors, as well as bug reports from the apps themselves.
The goal is to have all of this data logged effectively and then automatically sent to the relevant people for ongoing, continuous monitoring and control of the various systems, as well as CI/CD pipelines for the apps. And with that learning started well, I can now have it as a background task, along with the remaining courses starting soon, and begin to focus again on more of the UI/UX and coding tasks for the MOOVPAD Web App and new UI Interop objects.
If any of that made sense to anyone at all, please dm me with the explanation so I get it too 🙂
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.