Using wordpress as plugin repository for other wordpress websites

[Gentleman]

Hey i'm thinking about creating one main wordpress website with activated plugins that would serve as plugin repository for other websites. So basically i could buy plugin with GPL license and activate it on main wordpress website (repository) and then if plugin will be updated, this updated version would be pushed to other websites.

But
Even if i push plugin to other website it has to be activated on this website so i would have to null plugin and then push nulled version if plugin would need nulling to work correctly.

How would you approach this situation, maybe there is another better way to do this?

@NullMaster @TassieNZ @starliner @slvrsteele @phpcore

 

[starliner]

Hey i'm thinking about creating one main wordpress website with activated plugins that would serve as plugin repository for other websites. So basically i could buy plugin with GPL license and activate it on main wordpress website (repository) and then if plugin will be updated, this updated version would be pushed to other websites.

But
Even if i push plugin to other website it has to be activated on this website so i would have to null plugin and then push nulled version if plugin would need nulling to work correctly.

How would you approach this situation, maybe there is another better way to do this?

@NullMaster @TassieNZ @starliner @slvrsteele @phpcore

First you must create main web site as server for serving plugins core files. And the plugin which will you use, it must be modified as update requests with your main server api codes. Like wordpress repository. And than with api request between main and child web sites you must control versions with specified delays.

It can be done, but need to modify both plugin, and web sites

 

[guguk]

Hey i'm thinking about creating one main wordpress website with activated plugins that would serve as plugin repository for other websites. So basically i could buy plugin with GPL license and activate it on main wordpress website (repository) and then if plugin will be updated, this updated version would be pushed to other websites.

But
Even if i push plugin to other website it has to be activated on this website so i would have to null plugin and then push nulled version if plugin would need nulling to work correctly.

How would you approach this situation, maybe there is another better way to do this?

@NullMaster @TassieNZ @starliner @slvrsteele @phpcore

You need an extra plugin for API check-request. And other websites should install that plugin for checking updates regularly (with cron job) or themes if available.

"I think."

 

[Gentleman]

Actually i have already solved this problem but something now arised in my mind. Is it possible to use one license code for multiple websites even if it's suppose to work with only 1 domain? Some plugins have to be nulled to work properly and i'm wondering how could i make them work on other websites by activating them only on resource website... Any ideas?

 

[starliner]

you must null it if there was domain restriction in plugin