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

<div class="post-metadata">

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

</div>

Hmmm, I would be less pessimistic. You could also say that this could be a very large plugin.

The Custom Wizard plugin is so big It’s almost a separate app (especially on the front end).

There’s a lot of useful generic stuff written into Discourse you can reuse, eg User accounts framework and functionality, the deployment pipeline etc etc.

Also you can bend a lot of use cases around Discourse on the front end. Topics are your pages etc

The devil is in the detail here I think.

Just my 10 cents.

---

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