Skip to content
This repository has been archived by the owner on Oct 19, 2018. It is now read-only.

Support more app servers than simply 'rails server' #7

Open
explainer opened this issue Oct 5, 2017 · 2 comments
Open

Support more app servers than simply 'rails server' #7

explainer opened this issue Oct 5, 2017 · 2 comments

Comments

@explainer
Copy link

We need to be able to support other ruby web servers, like Puma, Thin, etc. There is a method for monkey patching which works (thanks @votiakov), but it is hardly a method to use in a product sense.

I suggest adding something to config/initializers/hyperloop.rb that allows a developer to list a set of servers to use. That way, debugging and development could use 'rails server' as it currently does, but also support others in the list above for production use, when a daemon install is important.

@catmando
Copy link
Contributor

catmando commented May 5, 2018

@explainer is this still an issue?

@janbiedermann
Copy link
Contributor

@catmando this depends on your latest hyper-operation patches to on_server?, that was the issue i believe

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants