Domain Aliases
-
I have pushed an initial implementation for this now. Essentially, you can add aliases which can be a wildcard or any other domain on Cloudron. As always the DNS, cert setup etc are all automated. I have checked with WP multisite and it works well (I am sure there are possibly package tweaks we have to do further). I will test EspoCRM and GitLab pages tomorrow.
-
@girish Cloudron simplicity - love it!
-
@marcusquinn I tested with EspoCRM portals today and it works well!
@girish Brilliant
Espo Portals are going to be a game-changer for me, I'm looking at Espo as a rapid web-app development for business, almost can't believe I overlooked it for so long. -
I have pushed an initial implementation for this now. Essentially, you can add aliases which can be a wildcard or any other domain on Cloudron. As always the DNS, cert setup etc are all automated. I have checked with WP multisite and it works well (I am sure there are possibly package tweaks we have to do further). I will test EspoCRM and GitLab pages tomorrow.
@girish said in Domain Aliases:
I have checked with WP multisite and it works well (I am sure there are possibly package tweaks we have to do further).
You da man! This was the big
boxchange to make it all possible. There are some subtle Multisite changes, that I'll submit as PR to WP Developer and WP Managed. They involve:-
Upgrading the databases of all subsites on on WP Update (by default, it only upgrades the primary sites database on upgrades and overlooks sub-sites which can cause conflicts) - and this requires only a few WP-CLI lines of code after a WP Update (it detects version changes and upgrades all sub-site databases right away to prevent any sites getting out of sync from the primary sub-site which automatically has it's database upgraded when needed).
-
The default WP-Cron script included in Cloudron's package runs every minute and disables Wordpress built-in Cron. Sub-sites need to be accounted for when disabling cron, and luckily, I wrote another WP-CLI that loops and runs the Cron Queue for each sub-site (if they exist).
-
(Optional) I'm writing a "Cloudron for Wordpress"
Must Useplugin to make sure if a domain gets changed from within Wordpress, it adds the new domain to the list of aliases in app locations within Cloudron's Dashboard. I see you added an API endpoint for this so it'll be easy enough for me to do, though a user will have to enter in a login token or app token into the WP plugin (UNLESS you'd like to automate this on install).
-
-
@girish said in Domain Aliases:
I have checked with WP multisite and it works well (I am sure there are possibly package tweaks we have to do further).
You da man! This was the big
boxchange to make it all possible. There are some subtle Multisite changes, that I'll submit as PR to WP Developer and WP Managed. They involve:-
Upgrading the databases of all subsites on on WP Update (by default, it only upgrades the primary sites database on upgrades and overlooks sub-sites which can cause conflicts) - and this requires only a few WP-CLI lines of code after a WP Update (it detects version changes and upgrades all sub-site databases right away to prevent any sites getting out of sync from the primary sub-site which automatically has it's database upgraded when needed).
-
The default WP-Cron script included in Cloudron's package runs every minute and disables Wordpress built-in Cron. Sub-sites need to be accounted for when disabling cron, and luckily, I wrote another WP-CLI that loops and runs the Cron Queue for each sub-site (if they exist).
-
(Optional) I'm writing a "Cloudron for Wordpress"
Must Useplugin to make sure if a domain gets changed from within Wordpress, it adds the new domain to the list of aliases in app locations within Cloudron's Dashboard. I see you added an API endpoint for this so it'll be easy enough for me to do, though a user will have to enter in a login token or app token into the WP plugin (UNLESS you'd like to automate this on install).
-
-
I try to set multisite wordpress.
but, I can't see aliases/location at wordpress app.
how or when can I set aliases ?
Thanks you very much ! -
I try to set multisite wordpress.
but, I can't see aliases/location at wordpress app.
how or when can I set aliases ?
Thanks you very much ! -
The multiste changes are ready. However, I can only publish the app next week. This week there is already an update on WP developer edition pending (the mail plugin was replaced).
Initial docs are at https://docs.cloudron.io/apps/wordpress-developer/#multisite . There is also a CLI tool to convert a site to multisite (just adding that to the docs).
-
The multiste changes are ready. However, I can only publish the app next week. This week there is already an update on WP developer edition pending (the mail plugin was replaced).
Initial docs are at https://docs.cloudron.io/apps/wordpress-developer/#multisite . There is also a CLI tool to convert a site to multisite (just adding that to the docs).
@girish said in Domain Aliases:
The multiste changes are ready. However, I can only publish the app next week. This week there is already an update on WP developer edition pending (the mail plugin was replaced).
Initial docs are at https://docs.cloudron.io/apps/wordpress-developer/#multisite . There is also a CLI tool to convert a site to multisite (just adding that to the docs).
Perfect! As soon as you release this, I'll get to work testing and integrating my multisite quality of life package adjustments and will do a PR for you after I'm finished testing and am satisfied it is ready for production.
PS. I've been frequenting this forum less this year than in fall - was there progress with @MooCloud_Matt in regards to repackaging Wordpress for Cloudron using a more efficient stack?
-
@girish said in Domain Aliases:
The multiste changes are ready. However, I can only publish the app next week. This week there is already an update on WP developer edition pending (the mail plugin was replaced).
Initial docs are at https://docs.cloudron.io/apps/wordpress-developer/#multisite . There is also a CLI tool to convert a site to multisite (just adding that to the docs).
Perfect! As soon as you release this, I'll get to work testing and integrating my multisite quality of life package adjustments and will do a PR for you after I'm finished testing and am satisfied it is ready for production.
PS. I've been frequenting this forum less this year than in fall - was there progress with @MooCloud_Matt in regards to repackaging Wordpress for Cloudron using a more efficient stack?
@lonk Yes, thanks! Would love to get it tested first before we announce it to the world
I will update this post once I publish it, but the changes itself are pushed to https://git.cloudron.io/cloudron/wordpress-developer-app/ if you want to build it on your own.For the more efficient stack, what I have seen is installing some file cache for pages like WP Total Cache totally boosts performance numbers. I am wondering if we should just install this by default.
-
@lonk Yes, thanks! Would love to get it tested first before we announce it to the world
I will update this post once I publish it, but the changes itself are pushed to https://git.cloudron.io/cloudron/wordpress-developer-app/ if you want to build it on your own.For the more efficient stack, what I have seen is installing some file cache for pages like WP Total Cache totally boosts performance numbers. I am wondering if we should just install this by default.
@girish If you were going to make anything default, it ought to be the officially supported WP Super Cache.
Despite it having a lesser review rating on wordpress.org because they're not actively soliciting positive reviews and targeting negative ones for removal or improvement because it's not commercial. We tried all of them and WP Super Cache was the best results, flexibility, only one supporting fragment caching, lots of hooks and good code quality.
Web Design https://www.evergreen.je
Development https://brandlight.org
Life https://marcusquinn.com -
@girish If you were going to make anything default, it ought to be the officially supported WP Super Cache.
Despite it having a lesser review rating on wordpress.org because they're not actively soliciting positive reviews and targeting negative ones for removal or improvement because it's not commercial. We tried all of them and WP Super Cache was the best results, flexibility, only one supporting fragment caching, lots of hooks and good code quality.
@marcusquinn said in Domain Aliases:
WP Super Cache
https://wordpress.org/plugins/wp-super-cache/ right? The one developed by automatic.
-
@marcusquinn said in Domain Aliases:
WP Super Cache
https://wordpress.org/plugins/wp-super-cache/ right? The one developed by automatic.
@girish For what it's worth, caching tools tend to be personal preference, so I'd refrain from making anything default in there if it were me making that decision, and maybe just include some general performance recommendations in the docs instead.
--
Dustin Dauncey
www.d19.ca -
@marcusquinn said in Domain Aliases:
WP Super Cache
https://wordpress.org/plugins/wp-super-cache/ right? The one developed by automatic.
@girish Yup, I don't think you can go wrong with the official one, it's as good as core and what they use on wordpress.com
-
@girish For what it's worth, caching tools tend to be personal preference, so I'd refrain from making anything default in there if it were me making that decision, and maybe just include some general performance recommendations in the docs instead.
@d19dotca
In my experience they tend to be more marketing and reviews bias preferences because the paid-pro versions afford to play to that game. I can only share what we went through testing them all and coming to conclusions.I also know that they can cause a lot of problems in hiding underlying inefficiencies, creating their own bugs, interfering with debugging.
Add in dynamic content and there really are no other options that will do fragment caching, so you either have full-page caching and no dynamic content or no caching and all the inefficiencies come back to haunt as soon as a user logs in and everything's uncacheable because one tiny part of a page is dynamic.
Granted, most Wordpress websites don't have Woocommerce or other functional features, but as people discover and add them, then then you have to come back to explain their caching plugin doesn't help for dynamic content and the whole stack needs revisiting.
I guess it comes down to what compelling difference would make one trust Automattic's core platform but not their caching methodology?
-
@lonk Yes, thanks! Would love to get it tested first before we announce it to the world
I will update this post once I publish it, but the changes itself are pushed to https://git.cloudron.io/cloudron/wordpress-developer-app/ if you want to build it on your own.For the more efficient stack, what I have seen is installing some file cache for pages like WP Total Cache totally boosts performance numbers. I am wondering if we should just install this by default.
@girish said in Domain Aliases:
For the more efficient stack, what I have seen is installing some file cache for pages like WP Total Cache totally boosts performance numbers. I am wondering if we should just install this by default.
Personally, I have no issues with the current stack (even without the caching plugin, honestly, REDIS is enough for me). I just know you were working with @MooCloud_Matt in revising the stack and since I've been gone for a bit, I wasn't sure if you guys ever came to any solid conclusions in his "Wordpress Stack Comparison" thread.
-
@d19dotca
In my experience they tend to be more marketing and reviews bias preferences because the paid-pro versions afford to play to that game. I can only share what we went through testing them all and coming to conclusions.I also know that they can cause a lot of problems in hiding underlying inefficiencies, creating their own bugs, interfering with debugging.
Add in dynamic content and there really are no other options that will do fragment caching, so you either have full-page caching and no dynamic content or no caching and all the inefficiencies come back to haunt as soon as a user logs in and everything's uncacheable because one tiny part of a page is dynamic.
Granted, most Wordpress websites don't have Woocommerce or other functional features, but as people discover and add them, then then you have to come back to explain their caching plugin doesn't help for dynamic content and the whole stack needs revisiting.
I guess it comes down to what compelling difference would make one trust Automattic's core platform but not their caching methodology?
@marcusquinn I agree to most of what you wrote. But just to be clear... my comment wasn't meant to be taken as to why one would or wouldn't trust Automattic's caching functionality, in fact it wasn't really meant to be about caching at all (though I admittedly didn't clarify that at all in my comment haha, my bad).
I fundamentally believe that we should strive to stay away from any kind of "bloat" and keeping it to only required plugins in the app package. This is for a few reasons (of course these are just my own opinions):
- The WordPress Dev app package should ideally be as close as possible to a default WordPress.org install in a LAMP server.
- The only plugins that should be included OOTB should be for fundamental requirements such as the SMTP plugin for sending emails.
- Any plugins that aren't requirements for WordPress to function OOTB, should not be included. This keeps the app package lean, and prevents plugin "bloat".
- Where do we draw the line of which plugins should be included and which should not? I think it's a fine line, and in my opinion should be placed right between "required" plugins and "nice-to-have" plugins. Maybe some disagree but I personally see caching plugins as "nice-to-have". There's a reason they aren't included OOTB in any WordPress installs.
- Caching plugins in particular have a history of causing unintended side effects, as you alluded to as well. And while you and I may already understand those side effects and know how to work around them, not everyone deploying WordPress will understand that and will inevitably run into issues between what they see in the backend vs frontend and not understanding why it's behaving that way, etc. To be fair, I suspect most people running the WordPress Developer edition will already be well aware of that whole dynamic, but not everyone will be.
I just fundamentally believe that the WordPress app package should only include required functionality, no nice-to-haves no matter how many people end up installing the nice-to-have plugins anyways. I think going down the route of including caching plugins (or other nice-to-have plugins) is the wrong route to take for the longevity of this app package.
Hopefully that makes sense.
--
Dustin Dauncey
www.d19.ca -
@marcusquinn I agree to most of what you wrote. But just to be clear... my comment wasn't meant to be taken as to why one would or wouldn't trust Automattic's caching functionality, in fact it wasn't really meant to be about caching at all (though I admittedly didn't clarify that at all in my comment haha, my bad).
I fundamentally believe that we should strive to stay away from any kind of "bloat" and keeping it to only required plugins in the app package. This is for a few reasons (of course these are just my own opinions):
- The WordPress Dev app package should ideally be as close as possible to a default WordPress.org install in a LAMP server.
- The only plugins that should be included OOTB should be for fundamental requirements such as the SMTP plugin for sending emails.
- Any plugins that aren't requirements for WordPress to function OOTB, should not be included. This keeps the app package lean, and prevents plugin "bloat".
- Where do we draw the line of which plugins should be included and which should not? I think it's a fine line, and in my opinion should be placed right between "required" plugins and "nice-to-have" plugins. Maybe some disagree but I personally see caching plugins as "nice-to-have". There's a reason they aren't included OOTB in any WordPress installs.
- Caching plugins in particular have a history of causing unintended side effects, as you alluded to as well. And while you and I may already understand those side effects and know how to work around them, not everyone deploying WordPress will understand that and will inevitably run into issues between what they see in the backend vs frontend and not understanding why it's behaving that way, etc. To be fair, I suspect most people running the WordPress Developer edition will already be well aware of that whole dynamic, but not everyone will be.
I just fundamentally believe that the WordPress app package should only include required functionality, no nice-to-haves no matter how many people end up installing the nice-to-have plugins anyways. I think going down the route of including caching plugins (or other nice-to-have plugins) is the wrong route to take for the longevity of this app package.
Hopefully that makes sense.
@d19dotca I'm inclined to agree that it might be something better documented - but more-so because caching problems can cause support burdens where they are a common source of issue for the uninitiated.
I like your suggestion that documentations have comments like "we tested this and it worked for us" sort of thing.
