# Is it possible to submit a forked version for managed hosting?
**URL:** https://meta.discourse.org/t/is-it-possible-to-submit-a-forked-version-for-managed-hosting/124030
**Category:** Development
**Created:** [7월 26, 2019, 9:42오전 UTC](https://meta.discourse.org/t/is-it-possible-to-submit-a-forked-version-for-managed-hosting/124030 "2019-07-26T09:42:46Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@pebble](https://meta.discourse.org/u/pebble)
#### Post date: [7월 26, 2019, 9:42오전 UTC](https://meta.discourse.org/t/is-it-possible-to-submit-a-forked-version-for-managed-hosting/124030/1 "2019-07-26T09:42:46Z")
Most of the context is in the title.
We are in the process of making some changes to the SSO login. The result is that a user can login without a redirecting away from the discourse site.
This is achieved by opening an iframe to the sso provider. And then only redirecting to the sso\_login url once that frame has returned a token.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [7월 26, 2019, 9:54오전 UTC](https://meta.discourse.org/t/is-it-possible-to-submit-a-forked-version-for-managed-hosting/124030/2 "2019-07-26T09:54:30Z")
Why wouldn’t you make modifications using the plugin architecture? Then the issue falls away.
---
### Author:  [@pebble](https://meta.discourse.org/u/pebble)
#### Post date: [7월 26, 2019, 9:58오전 UTC](https://meta.discourse.org/t/is-it-possible-to-submit-a-forked-version-for-managed-hosting/124030/3 "2019-07-26T09:58:07Z")
I’m still looking through the source so maybe it will work. but getting more convinced the plugin architecture doesn’t give me quite enough control to achieve what I need.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [7월 26, 2019, 10:20오전 UTC](https://meta.discourse.org/t/is-it-possible-to-submit-a-forked-version-for-managed-hosting/124030/4 "2019-07-26T10:20:18Z")
I think you have to consider the architecture and not get too insistent on having an embedded iframe, for example.
Pop-up login windows and callbacks are standard practice, for example, and very straightfoward with a plugin.
Managing a fork of Discourse would be an utterly inefficient approach and an ongoing nightmare. In contrast, if built right, plugins can be very robust to change and require much less maintenance.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [7월 26, 2019, 11:54오전 UTC](https://meta.discourse.org/t/is-it-possible-to-submit-a-forked-version-for-managed-hosting/124030/5 "2019-07-26T11:54:43Z")
Those who tried to maintain a forked version of Discourse are very sorry. You’ll either need to have a full time developer or integrate changes or never upgrade. And in the end you’ll move to a plugin.
I suspect that you can do what you need in a plugin, or could make it do whet you need through a PR. You should either explain why you think you can’t solve your problem in a plugin or post in #Marketplace for help.
I manage discourse as a part of my business ([Redirecting…](https://www.literatecomputing.com/discourse-server-maintenance/)) and have a few clients who need custom configuration but cannot afford enterprise level hosting. I would love your business, but wouldn’t consider supporting a fork.
---
### Author:  [@pebble](https://meta.discourse.org/u/pebble)
#### Post date: [7월 26, 2019, 12:13오후 UTC](https://meta.discourse.org/t/is-it-possible-to-submit-a-forked-version-for-managed-hosting/124030/6 "2019-07-26T12:13:40Z")
A plug in would be better, if possible.
I will keep investigating, it is useful to see how separate our protocol is from OAuth anyway.
---
### Author:  [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [7월 26, 2019, 8:49오후 UTC](https://meta.discourse.org/t/is-it-possible-to-submit-a-forked-version-for-managed-hosting/124030/7 "2019-07-26T20:49:48Z")
I can also confirm that at [Discourse.org](http://Discourse.org) we would not host a fork of Discourse either, even on our Enterprise Plan. You must create plugins/theme components for your changes