Experimental App Update: WordPress + Powerbox <3
15 views
Skip to first unread message
Jacob Weisz
Feb 22, 2023, 4:06:54 AM2/22/23
to sandst...@googlegroups.com
Hey everyone,
I am not able to push this to the experimental market quite yet, but I've got a "I believe it works okay" re-release of WordPress! The key thing here is it includes Ian's powerbox-http-proxy, so that you can make outgoing web requests from inside the WordPress admin interface! This likely unlocks a *lot* of functionality, and will add support for a lot of plugins, but the key thing is that you can now import WordPress blogs *and their media* with the built-in import tool!
Probably the biggest caveat right now is that the call-home requests to api.wordpress.org are super aggressive. You'll either want to allow it (which is needed for a bunch of useful things presumably), or give it a fake URL to block it. Unfortunately there's currently no way in the Sandstorm UI to revoke either of those decisions with your grain, and punting on granting the request will mean cancelling... many... many... powerboxes. I'm very interested in finding WordPress config variables that will reduce the call-homes without having to make it impossible to reach wordpress.org, as I'd like to allow plugin updates and such to happen trivially through the UI.
The current release is also still version 4.9.8, the last release shipped by the previous package maintainer. The way this package is updated is... rough, and I wanted to accomplish my main goal first of building it, fixing the packaging bitrot, and implementing powerbox support. I'll be looking to start shifting the package up to newer releases shortly. If anyone else is interested in good WordPress support and wants to help me on this one, feel free to reach out.
You can download the SPK here:
https://github.com/sandstormports/wordpress-sandstorm/releases/tag/v18
--
Jacob Weisz
in...@jacobweisz.com
I am not able to push this to the experimental market quite yet, but I've got a "I believe it works okay" re-release of WordPress! The key thing here is it includes Ian's powerbox-http-proxy, so that you can make outgoing web requests from inside the WordPress admin interface! This likely unlocks a *lot* of functionality, and will add support for a lot of plugins, but the key thing is that you can now import WordPress blogs *and their media* with the built-in import tool!
Probably the biggest caveat right now is that the call-home requests to api.wordpress.org are super aggressive. You'll either want to allow it (which is needed for a bunch of useful things presumably), or give it a fake URL to block it. Unfortunately there's currently no way in the Sandstorm UI to revoke either of those decisions with your grain, and punting on granting the request will mean cancelling... many... many... powerboxes. I'm very interested in finding WordPress config variables that will reduce the call-homes without having to make it impossible to reach wordpress.org, as I'd like to allow plugin updates and such to happen trivially through the UI.
The current release is also still version 4.9.8, the last release shipped by the previous package maintainer. The way this package is updated is... rough, and I wanted to accomplish my main goal first of building it, fixing the packaging bitrot, and implementing powerbox support. I'll be looking to start shifting the package up to newer releases shortly. If anyone else is interested in good WordPress support and wants to help me on this one, feel free to reach out.
You can download the SPK here:
https://github.com/sandstormports/wordpress-sandstorm/releases/tag/v18
--
Jacob Weisz
in...@jacobweisz.com
Jake W
Mar 3, 2023, 1:33:55 AM3/3/23
to Sandstorm Development
Pushed a small update to this at https://github.com/sandstormports/wordpress-sandstorm/releases/tag/v19
v18 worked okay for me for importing a blog, but immediately failed out with an SSL error when I tried updating plugins from Wordpress.org. Turns out, WordPress stores it's own CA bundle, so I needed to tie the proxy's CA cert into that. With this update, I was able to update themes and plugins without issue. I suspect all HTTPS may have been broken, but the website I had been importing accepted HTTP or HTTPS.
Reply all
Reply to author
Forward
0 new messages