Module: ProcessWire Core Upgrade

[flydev]

21 hours ago, wbmnfktr said:

No automated updates (I am not an adrenalin enthusiast)!

If you end up writing something with github action / webhooks / etc to automate things on a staging setup, and rockmigrating rolling back if your written test cases fail, please do not hesitate to share it with us  (I am not sending subliminal messages) ?

12 hours ago, monollonom said:

non tested code written from my phone

I would like to be able to give you more likes ??

[bernhard]

On 5/13/2023 at 10:27 AM, monollonom said:

Something like:

$wire->addHook("LazyCron::everyMonth", function(HookEvent $event) {

1st thought: Wow, that is brilliant!!!

2nd thought: We have to build a module from/for that!!

3rd thought: Hm... How would I actually use it. What fields would we need to have? Would I actually want to update, just because there are updates? Isn't it actually more dangerous to update modules than to just leave them untouched? I mean - I'm also keeping all modules up to date usually, but in general that happens during development so I'm hands on that project and I instantly see if something breaks. So how are you thinking to use that @wbmnfktr and others?

I'm also happy to read about RockMigrations, though I wonder if the use case would be a good one for RM... It's actually built more for the opposite of reverting changes. It's really good add adding/changing things, but I'm usually reverting things just by git reset and/or "php rockshell db-restore"

I really like the idea of having some kind of PW Assistant (or copilot) that notifies the admin about important things. It would be to define thought what those important things could be. I could think of several things like monitoring file count, file size, db site, file permissions etc. of an installation. Maybe also a 404 monitor or such. Maybe I'm already too many steps ahead, but I think if I really wanted to add something like this it would need to be something really useful and just updating for the sake of being up to date is just not enough for me ? 

Edit: Related: https://processwire.com/talk/topic/28499-automation-hooks-make-life-easier/#comment-232765

[dab]

I love this module, thanks. It's makes upgrading so easy. Across a few sites that I've upgraded PW core (the latest was from PW 3.0.210 to PW 3.0.246) I'm getting an error showing:

SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'created'.

I spotted using "Tracy/Adminer" that some Module "created dates" were showing as created "0000-00-00 00:00:00", but replacing this with real date/times made no difference.

It's not affecting functionality, but curious how to identify the cause & find a fix! Thanks.

Ha, sorted it! Edited the sql file directly "find & replace" 0000-00-00 00:00:00 etc with a valid date & it's fixed! 

 

Edited March 6, 2025 by dab
fixed!

[maximus]

@ryan, can you add cli command for quick updates without pushing for each button ?

[adrian]

@maximus - it hasn't been maintained in quite some time (and probably does need some work on some features), but https://github.com/adrianbj/ProcessModuleToolkit provides a way to upgrade all with one button click. Not suggesting your idea wouldn't be nice as well though.

[maximus]

The module may not have received any updates in the last five years, but it works reliably. I use it as a must-have for updates. 

Thanks for sharing the link - I hadn't heard of it before.

[Jonathan Lahijani]

One minor nitpick with this module is that if you're running the dev version of ProcessWire (lets say version 3.0.123) and that version receives additional commits/updates but without a version bump, you can't "upgrade" to it given how this module works.  You can only upgrade when 3.0.124 dev version is available.

Not a big deal for me since I have a bash script that takes care of pulling the latest from GitHub, however it would be nice to support getting the absolutely latest bleeding edge version with this module.

[adrian]

@Jonathan Lahijani - are you talking about the PW Upgrade module, or my old Toolkit module?

[Jonathan Lahijani]

1 hour ago, adrian said:

@Jonathan Lahijani - are you talking about the PW Upgrade module, or my old Toolkit module?

The PW Upgrade module.

[adrian]

3 minutes ago, Jonathan Lahijani said:

The PW Upgrade module.

I use it all the time to upgrade to the very latest core commits - it doesn't need a version number jump for me. I just wish the modules worked the same way.