View in #programming on Slack
@laurence: @cogginsalan Did you get a proper way of keeping the plugins updated on a private server? Please share if so.
@jnylen: @laurence you should still be able to go to the dashboard and update? or maybe I’m not understanding
@slack1891: @jnylen, it was for serving updates from a remote server (ie, for our GitHub’d plugins)… @laurence, this is the plugin that @cogginsalan used:
https://genbumedia.com/plugins/fx-updater/
f(x) Updater - WordPress Plugin by Genbu Media
@jnylen: ah
@slack1891: I’ve also been giving it a whirl - it works pretty well.
Stop-gap solution for pre-CP-plugin-dir 
@jnylen: there’s also https://github.com/afragen/github-updater
afragen/github-updater
serves the updates from GitHub etc
we’ll probably take a lot of inspiration from this plugin with the ClassicPress directory
if some of y’all want to dissect it and learn how it works, even better - I’ve not looked yet
that’s a separate plugin - there is also https://github.com/radishconcepts/WordPress-GitHub-Plugin-Updater which is a class you include with each plugin
radishconcepts/WordPress-GitHub-Plugin-Updater
@slack1891: Cool. The one I linked is perhaps a combo of the 2… the plugin provides the server and a class provides the client
@jnylen: using a CP site as the update server instead of GitHub, right?
@slack1891: either or
@jnylen: ah
ok going to save this to a thread in the plugin directory subforum
@slack1891: For sure… there’s a nice array of already-invented-wheels out there to cherry pick from.
