Today I was asked to integrate @Code_Potent plugin updater in one of my plugins
I ended up not doing it because decided to push it to WP repo as well mainly just to use their update mech
Also because if each and every cp developer has to setup server to serve updates, that costs money and also isn’t really safe.
So my thought here, wouldn’t it be possible to integrate @Code_Potent plugin updater in a server managed by classicpress, a central server for all our plugins, and then ship updates from there?
That would allow us to ship our updates now without waiting for (years probably) cp to break version and add its own plugin list in core.
The problem is right now unless you have a dedicated server that you use just to ship cp updates (plugin related) you really can’t ship updates
Unless you go with the plugin to WP, but then you can’t use cp doc links, cp names, and the like because you probably risk the plugin being refused.
Like, I can’t send a “for classicpress” plugin to WP repo and not even test it with 5.8
So, is it possible to integrate said (or similar) update mechanism in cp servers to help our developers push updates to our users from a safe, centralized system without huge efforts?