From a UI point of view, maybe keep App Store as your supported Managed Apps and have separate section, maybe just called "3rd Party"
Maybe an "Add Repositories" button to add Gitlab Group or Repo URLs?
@girish How about embeding it with Unmanaged WP installation as of with redis? Is this something that could be done?
I personally totally agree with not messing too much with third parties packages from cloudron box, especially as, indeed, you'd have no control on future devs of such outsider apps and thus no control on the outcomes. I believe what you are doing already is extraordinary imho so as some say "if a thing works well, don't f.... try to 'fix' the thing..." lol
MooCloud_Matt last edited by
What's the status here guys? I came here wanting to use cloudron wp with OLS, anyway we can get this online?
ruihildt last edited by
I'm a bit disappointed as I don't think this was mentioned in any previous public discussions on the subject.
@MooCloud_Matt Would you consider sharing your code with the community? I'm not sure anyone here is directly competing with your business to be honest.^^
Having been through a of of WP performance testing and comparison in the past, including OLS, I really wouldn't feel your missing out, as we neither managed to get performance as good as standard Nginx & Apache, and it really didn't seem either broadly known by devs or any more than just good default settings that can be done and more with Nginx & Apache anyway.
Long story short, I don't think anyone is missing out without this as the Cloudron WP stack is already very good, and any performance issues are more than likely with the codebase running on whatever stack, and within that most likely sql query efficiencies in certain plugins that tend to only show themselves slow when you add content.
First think I recommend everyone should try is disable
open_basedir, it was one of the simplest and most impactful changes we made for the least effort.
We also use a technique similar to that offered with this plugin for only loading what's needed to render each page, before any caching:
Gonzales or Clearfy Asset Manager does similar things - but like all these things, you need to know or at least bear in mind what you're doing as whenever you unload things you create debugging blindspots:
If, after all of that optimisation, you still think OLS is needed, there's no harm in trying other than time but I suspect most will finds that OLS won't help with performance as much as optimising what is asked of the server by the app first.
I haven't done extensive testing with OLS, but to add to what @marcusquinn said, the main speed benefits come from caching (which OLS does by default). With WP, if you install WP Super Cache or equivalent, you get very good numbers on Cloudron. It's on my list to investigate integrating Super Cache or something as the default. But these caches always have some corner cases where you have to click the "clear cache" button manually and then we have to inform users about all this. This is why we have left the choice to the user for now.
@girish Agreed - see caching as more of a problem than a solution, and it usually masks more problems than it solves. Caching is for scaling traffic but full-page caching can't help with dynamic content.
I can't say we have all the solutions but we have been down the road of trying so many solutions and always come back to the fundamentals that it's the quality of the plugins used and their query efficiency that has the most impact, and we focus on WP Admin speed foremost because that's generally heavier and slower, so if we get that right the front-end is usually fine.
MooCloud_Matt last edited by
yes and no, OLS/LS is objectively more efficient over apache, and this make it more performant then apache.
Berceuse as Nginx it can serve static file without wake up a php, that apache is using for every request on a WP.
But as i already say sometimes a good server lvl optimization of nginx is performing as well but is not easy to setup, OLS or LS offer LSCache to do all the config from WP dashboard.
WP plugin are not the best way to go, because they just let the call be managed by a PHP, many like Cache enabler, just create a HTML copy of the website, that is more performant no elaboration needed by db or php, but if you use apache you will wake up PHP anyway so CPU and RAM wasted.
We are in Open Beta for OLS, if you want we can provide you the image.
But for now the code is closed sourse, it will be realise with a custom licenses that is open source but not commercially usable by MSP or ISP to offer WordPress as a Service or PaaS.