search

intercity / intercity-classic

Simple web control panel for hosting Rails apps.
https://intercityup.com
MIT License
36 stars 4 forks source link

Add support for more webservers #17

Open jvanbaarsen opened 9 years ago

jvanbaarsen commented 9 years ago

At this point we only support Passenger, which is a great default, but it would be nice if we can also start supporting webservers like Unicorn and Puma.

Best case would be to have this in a generic way. I.e. add a intercity.yml file to your project for example, and let people configure what webserver they want to use. And use Passenger by default.

michiels commented 9 years ago

Cool I think that makes sense. For Chef configuration/provisioning I do think that it should be defined in the web interface when you set up your app, because all other web servers need custom configuration file generation on the Chef run too. We could of course provide some way to import your existing project and read config values from an intercity.yml.

jvanbaarsen commented 9 years ago

@michiels Hm yeah thats right. Somehow I sometimes feel like the Chef setup is biting us sometimes :D But yeah, having it in the webinterface for now makes sense

michiels commented 9 years ago

Yeha. Chef adds a little overhead in that part. However, currently chef allows us to make use of all the community best practices and standards, and offer people a way to keep managing their servers when they move away from us. And of course chef-repo is great marketing :D

I think in that sense chef-repo still weighs on the positive side in terms of use.

jvanbaarsen commented 9 years ago

@michiels Oh yeah, I was not saying we should replace chef :P just that it gets in the way sometimes. Benefits heavily outweigh the downsides though :dancers: