I might be being really stupid here.... but.... what on earth is 'mdeploy'?
No you are not being dense at all ...
https://docs.moodle.org/35/en/Automatic_updates_deployment
It originally used the moodle code directory.
Then moved to moodledata/mdeploy/ - right where one could easily see/find it ... included
a mdeploy.log - which I would tail -f when using.
And now moved again ... deeper into moodledata/temp/core_plugin/code_manager/
Prefer git for installations and updates to the core code myself ... would love to do the same for all addons, but have had trouble finding the 'right' code git repo for addons at one time.
Plugin downloads from https://moodle.org/plugins/ one has to follow the source control URL for a plugin and acquire the git URL.
Would be nice to see that git URL somewhere but understand that might be a future improvement way on down the road.
'spirit of sharing', Ken
Oh right... as I've probably mentioned, not a fan.
Yeah, I know. But am thinking that, if perfected, it could save the moodle admin noobie from some headaches ... maybe those that remotely host with no desire to use ssh/cli.
How many times have we seen, in these forums, either a botched install of a plugin where it was done 'manually' (not CLI, but cPanel FileManager) OR even, a botched update or upgrade due to an incompatible plugin either copied to the wrong location or caused the update/upgrade to fail ... 'whale fail'.
Yes, Rick ... he ought to be along any minute now with his methods ... know one 'pre-package' something local and do it that way. I, however, want not to use local machine at all. "Nuttin'" but server.
To each their own, I guess!
But thanks for asking and responding!
'spirit of sharing', Ken
My problem is that it positively encourages admins to run insecure sites.
As you say, this tends to be exactly the same group of users who won't have much knowledge about server security.
I know that other well known applications do this (Wordpress I'm looking at you). But I know experienced server admins who will not touch the likes of Wordpress.
It also relies on plugin administrators keeping their info up to date in the plugins database.
Good points!
Yep, WordPresses and Joomla's too boot!
But that's why some 'consultants' can actually make a living ... uhhhh, which isn't me, BTW.
'spirit of sharing', Ken
So, Ken...
Did you ever get your answer about mdeploy? I have a moodledata directory that has seen many upgrades. I am now setting up a new server for 3.5 and I would like to trim the fat .
All the best,
Mathieu
No, never did. Believe the proper place for mdeploy files, etc. is in moodledata directory. Have a server that uses some 'big' plugins ... at least the zips are larger than most ... and have noticed/experienced they didn't update well via GUI mdeploy. Seem to get stuck after the current code plugin directory is removed ... which means half way. Can see the new code zip present but no 'activity' towards using it - at least I've not found a way to see that activity.
Anyhoo, Have resorted back to manual updates for those via hide, wget, php script in admin/cli.
Would assume that once the DB is updated with version information etc. that all those directories not really needed. There is currently no method via the GUI to use those previous versions in a 'rollback' as far as I know/can see.
However, my experience may not be yours! So on the side of caution, one could archive, save out to another handy location, in case I was wrong!
My 2 cents ...
'spirit of sharing', Ken