The discussion revolves around installing Discourse via Docker on an existing CentOS cPanel server running Litespeed, rather than Apache. Serb asks whether the standard installation steps would work, and pfaffman clarifies that the standard guide won’t apply, requiring manual setup with a Litespeed reverse proxy. Serb then inquires about deploying Discourse in a subfolder or subdomain of an existing Litespeed site. pfaffman confirms subfolder deployment is possible but not recommended due to added complexity and minimal SEO benefits, referencing subfolder support with Docker for further details.
If I follow the installation steps here:
how would that work out with my existing CentOS cPanel server running Litespeed instead of Apache as a webserver, with a dozen other websites on the server already?
What tweaks might I have to perform to make this Discourse install work properly on just one of those sites that requires it?
You can’t follow those steps. You’ll have to configure it manually and make light speed reverse proxy. See How to set up Discourse on a server with existing Apache sites as an example. If that server has less than 4gb of ram, I’d recommend that you spin up another so that you can do it the easy way.
Ok… but it CAN be set up in a subfolder of an existing website that’s already running on Litespeed, right?
Or at least mapped to a subdomain of that existing site (running on Litespeed) somehow, no?
Or not at all?
Yes, you can do a subfolder, but it’s really not recommended. It adds lots of complexity and mostly no one believes that using a subfolder has SEO advantages, best I can tell. That said, I think that some hosted client(s) has subfolder, so it should work.
See Subfolder support with Docker for more information.