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

<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:37 UTC](https://meta.discourse.org/t/using-discourse-as-one-part-of-a-larger-rails-app/155312/9 "2020-06-19T05:37:13Z")

</div>

I took a brief look at plugins. I prefer to use a different JS framework than Ember (I’m a svelte fanboy), and I’m a little concerned this will add a layer/interface to the discourse rails app (which I’m unfamiliar with) and make troubleshooting more complicated for me. I’m leaning towards keeping this as a separate app. I know rails pretty well (and proxying rails apps well), but don’t know discourse yet, and feel like I will have fewer blocks if I go down this route.

---

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