Also notice (from your gist) your app won't be forced to run chrooted, because httpd (chrooted) would talk to uWSGI which doesn't need to be, you can place the FastCGI socket under /var/www or serve it under 127.0.0.1.
2017-01-12 5:43 GMT-02:00 Roberto De Ioris <[email protected]>: > >> Hi, >> >> My Ruby on Rails app currently runs Nginx and Puma, however I'd like to >> replace Nginx with OpenBSD's native httpd which would involve using uWSGI >> as well. But, to be frank, I am super confused as to how I'm supposed to >> go >> about doing that as there is little to no docs on the subject apart from >> uWSGI's own docs which I find a wee bit overwhelming. > > > Hi, unfortunately OpenBSD httpd is relatively new so i am not surprised to > find really few docs. On the other side i have lot of customer using uWSGI > with Ruby On Rails, the support is really strong, but never became > something of 'mass use' like with python or perl. So you are pretty on > hard-paths :) My suggestion is starting with deploying your rails app with > uWSGI alone. The advantage is that uWSGI supports really old ruby/rails > combos so generally it is a good thing (in the long term) to invest on it. > > > -- > Roberto De Ioris > http://unbit.com > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi -- Daniel Nicoletti KDE Developer - http://dantti.wordpress.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
