# Deploying discourse on server already running another rails app

**URL:** https://meta.discourse.org/t/deploying-discourse-on-server-already-running-another-rails-app/38467
**Category:** Self-hosting
**Created:** [25 Janeiro , 2016 19:48 UTC](https://meta.discourse.org/t/deploying-discourse-on-server-already-running-another-rails-app/38467 "2016-01-25T19:48:34Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [25 Janeiro , 2016 20:23 UTC](https://meta.discourse.org/t/deploying-discourse-on-server-already-running-another-rails-app/38467/2 "2016-01-25T20:23:47Z")

</div>

The usual setup is to use a reverse proxy listening on port 80 that (maybe does SSL and) routes requests to the different applications. It’s not too hard to set up, and we have a nice tutorial by @riking for this:

> [@Run other websites on the same machine as Discourse](https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247):
>
> @pfaffman edited this heavily 2022.02.24. Blame me if it’s broken. If you want to run other websites on the same machine as Discourse, you need to set up an extra NGINX or HAProxy proxy in front of the Docker container. NOTE: This is for advanced admins This guide assumes you already have Discourse working - if you don’t, it may be hard to tell whether or not the configuration is working. You cannot use ./discourse-setup to set up Discourse if another server is using port 80 or 443. You will…

---

_[View the full topic](https://meta.discourse.org/t/deploying-discourse-on-server-already-running-another-rails-app/38467)._