# Using discourse as one part of a larger rails app?

**URL:** <https://meta.discourse.org/t/using-discourse-as-one-part-of-a-larger-rails-app/155312>\
**Category:** Development\
**Created:** [19 juni 2020 om 05:03 UTC](https://meta.discourse.org/t/using-discourse-as-one-part-of-a-larger-rails-app/155312 "2020-06-19T05:03:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Chris\_Dawson](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chris_dawson/32/184486_2.png) [@Chris\_Dawson](https://meta.discourse.org/u/Chris_Dawson)\
**Post date:** [19 juni 2020 om 05:10 UTC](https://meta.discourse.org/t/using-discourse-as-one-part-of-a-larger-rails-app/155312/3 "2020-06-19T05:10:29Z")

</div>

That’s great. I’m glad to know up front that this is not something recommended, saves me the trouble of trying it and failing miserably!

Ok. It sounds like the best way is to use two rails apps (discourse and my custom app) behind a reverse proxy.

After consideration, it seems like keeping two databases here is a better option to make sure my app does not update the discourse db in a bad way that discourse authors never intended.

Thank you.

---

_[View the full topic](https://meta.discourse.org/t/using-discourse-as-one-part-of-a-larger-rails-app/155312)._
