-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add release engine for WordPress #904
Comments
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With all the WP drama going on, I think providing a release engine for commercial WordPress plugins and themes makes sense. I personally don't know a lot about the internals of the WordPress update system, but I'm opening this issue to document. We should be able to create an engine that responds in WP's expected update format, whatever that may be.
Implement similar to #478. I'd prefer a
wp
subdomain, to avoid any trademark issues. See #679 for implementation of PyPI, and #753 for Tauri. The Tauri one will likely be the most helpful for reference, since the PyPI included a lot of noisy ground work.Helpful resources:
Other resources:
In the end, I want a customer to be able to upload a plugin or theme
.zip
to the distribution API we already have, and allow their end-users to get automatic updates for the plugin or theme like they would from the WP.org repo.Implementation should include integration tests. lmk of any questions.
The text was updated successfully, but these errors were encountered: