# 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:** 6

<div class="post-metadata">

**Author:** ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)\
**Post date:** [19 juni 2020 om 05:33 UTC](https://meta.discourse.org/t/using-discourse-as-one-part-of-a-larger-rails-app/155312/6 "2020-06-19T05:33:24Z")

</div>

Benefits of having a separate app - we can support you better here, and any updates Discourse does won’t break your app side of things.

Benefits of having the site be a “large discourse plugin” - you get all the bells and whistles and helpers available in Discourse (all the user management stuff as well) which is not to be underestimated.

It’d be cool depending on what you’re building - I think @justin wants to caution you about the potential maintenance overhead you take on. There’s no way we can fully support you if you’re scaffolding on to Discourse directly, and all of our internal helpers and schemas are Subject To Change™ so it _could_ be more trouble than it’s worth. (Depending on what you’re building, of course! It could also easily be worth the trouble 😉 )

---

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