# Rails server --daemon and plugins

**URL:** https://meta.discourse.org/t/rails-server-daemon-and-plugins/56291
**Category:** Development
**Created:** [January 24, 2017, 8:41pm UTC](https://meta.discourse.org/t/rails-server-daemon-and-plugins/56291 "2017-01-24T20:41:52Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![pieceOpiland](https://avatars.discourse-cdn.com/v4/letter/p/a88e57/32.png) [@pieceOpiland](https://meta.discourse.org/u/pieceOpiland)
#### Post date: [January 24, 2017, 8:41pm UTC](https://meta.discourse.org/t/rails-server-daemon-and-plugins/56291/1 "2017-01-24T20:41:52Z")

</div>

I’ve followed the instructions at [Install Discourse on macOS for development](https://meta.discourse.org/t/beginners-guide-to-install-discourse-on-mac-os-x-for-development/15772) to install a development environment of discourse. I’ve also installed the discourse-solved plugin, and everything works when I run: `bundle exec rails server`.

I wanted to run discourse with rails’ built in daemon. However, when I run the command `bundle exec rails server --daemon`, the discourse-solved plugin no longer seems to function correctly. For example, the option to accept a post as a solution is no longer available.

Does anyone have advice on how to get the plugin working correctly as a daemon in this fashion, or whether or not I should forgo this daemon mode and find a better strategy?

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [January 24, 2017, 8:53pm UTC](https://meta.discourse.org/t/rails-server-daemon-and-plugins/56291/2 "2017-01-24T20:53:27Z")

</div>

This happens indeed, but since I’m used to run a terminal multiplexer (tmux, byobu) I never found it myself.

---

<div class="post-metadata">

### Author: ![pieceOpiland](https://avatars.discourse-cdn.com/v4/letter/p/a88e57/32.png) [@pieceOpiland](https://meta.discourse.org/u/pieceOpiland)
#### Post date: [January 24, 2017, 9:07pm UTC](https://meta.discourse.org/t/rails-server-daemon-and-plugins/56291/3 "2017-01-24T21:07:01Z")

</div>

Ah! Nice! I was able to work around this issue with multiplexing, thanks!!

---

<div class="post-metadata">

### Author: ![Bill\_Wang](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bill_wang/32/93970_2.png) [@Bill\_Wang](https://meta.discourse.org/u/Bill_Wang)
#### Post date: [April 8, 2018, 3:04pm UTC](https://meta.discourse.org/t/rails-server-daemon-and-plugins/56291/4 "2018-04-08T15:04:07Z")

</div>

yes, I got similar problem.  
if run rails in deamon,  
I got " uninitialized constant Jobs::BotInput" when post a new topic.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [April 9, 2018, 1:47am UTC](https://meta.discourse.org/t/rails-server-daemon-and-plugins/56291/5 "2018-04-09T01:47:52Z")

</div>

Yeah this is the reloader, it is not super plugin friendly, to say the least

When this happens you sadly have to stop everything and relaunch

@tgxworld we should probably put a hack in place to compensate for bot… what happens is the job base class gets reloaded nuking the bot input job which never gets reloaded.
