I've got somewhat strange situation that I don't believe has been discussed in the forums thus far and I would like to ask for some guidance from the dev community about best practices for maintaining the Moodle plugins with both git and the 'install plugins' pages from the site.
For context, I am the newly minted tech-lead for this team, am a dev ( postgres + postgREST + elm.js for my fave/choice webstack ), and am also a sysadmin. But I am new to moodle because the previous the previous tech-lead for this was taken off the project due to sudden/unexpected long-term medical leave.
So, I'm familiar with the moodle plugin ecosystem now but I'm trying to get more familiar with the git workflows because we have changes on the test-server's filesystem that are not in git because they were installed from zip files using the site's plugin features.
Ultimately, I need to know a bit more about how to sync up the git repo, the locally modified filesystem, and also best practices for using git submodules moving forward.
In short, I think everything I need to know could be answered from a technical perspective with a full CI/CD answer to the following:
- what, if anything, does an admin/dev need to do on the running/production server to use the code from a git submodule and present it to the running site as a fully-functioning plugin?
If my question is totally off-base and doesn't represent a proper understanding of the real architecture then please do send some lovely nulledge my way and I'll be happy to read up on whatever I'm missing.