# Installing for production via Docker on existing server with Litespeed?

**URL:** https://meta.discourse.org/t/installing-for-production-via-docker-on-existing-server-with-litespeed/225420
**Category:** Self-hosting
**Created:** [April 27, 2022, 12:35pm UTC](https://meta.discourse.org/t/installing-for-production-via-docker-on-existing-server-with-litespeed/225420 "2022-04-27T12:35:24Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Serb](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/serb/32/258185_2.png) [@Serb](https://meta.discourse.org/u/Serb)
#### Post date: [April 27, 2022, 12:35pm UTC](https://meta.discourse.org/t/installing-for-production-via-docker-on-existing-server-with-litespeed/225420/1 "2022-04-27T12:35:24Z")

</div>

If I follow the installation steps here:

> <https://github.com/discourse/discourse/blob/main/docs/INSTALL.md>

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?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 27, 2022, 12:49pm UTC](https://meta.discourse.org/t/installing-for-production-via-docker-on-existing-server-with-litespeed/225420/2 "2022-04-27T12:49:57Z")

</div>

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](https://meta.discourse.org/t/how-to-set-up-discourse-on-a-server-with-existing-apache-sites/30013) 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.

---

<div class="post-metadata">

### Author: ![Serb](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/serb/32/258185_2.png) [@Serb](https://meta.discourse.org/u/Serb)
#### Post date: [April 27, 2022, 1:07pm UTC](https://meta.discourse.org/t/installing-for-production-via-docker-on-existing-server-with-litespeed/225420/3 "2022-04-27T13:07:03Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 27, 2022, 3:10pm UTC](https://meta.discourse.org/t/installing-for-production-via-docker-on-existing-server-with-litespeed/225420/4 "2022-04-27T15:10:04Z")

</div>

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](https://meta.discourse.org/t/subfolder-support-with-docker/30507) for more information.
