thin

Should I use thin or unicorn on Heroku Cedar

这一生的挚爱 提交于 2019-12-02 15:24:44
I recently 'upgraded' my app to the cedar platform on heroku. By default I am using thin as a web server. But I have always been tempted to use unicorn for concurrency and having my dyno dollar go father. But I worry there are some gotchas in using something other than Thin. Does anyone have real life experience with this decision? Thanks! Jonathan Notes: This was the article that got me excited about the idea: http://michaelvanrooijen.com/articles/2011/06/01-more-concurrency-on-a-single-heroku-dyno-with-the-new-celadon-cedar-stack/ I know every app is different, and that you should build a

Facing intermittent 404 issue when calling Rails API

会有一股神秘感。 提交于 2019-12-02 04:21:36
I have banged my head on this for 2 days now and i dint find any luck yet. Looking for help on this. The issue: Front End makes 10 similar XHR requests ( for different users ) to my Rails API and few of the requests randomly fails with 404 status code. My Observations: If i make the same request again, It passes. I dont see any trace of 404 requests even hitting my server ( using logs ). I do see different response headers for 200 and 404 ( mentioned below ) and i see cowboy ( https://github.com/heroku/cowboyku , https://github.com/heroku/vegur ) server for 404 requests. I run my rails

Ruby on rails: force_ssl not redirecting from http to https when using thin start --ssl

☆樱花仙子☆ 提交于 2019-12-02 00:39:06
问题 I have been trying to configure my rails project to use SSL (as application wide) with thin (by adding thin gem and placing config.force_ssl = true to application.rb ) but as a result, I have an annoying problem. When I start my rails server using rails s and try to access http://localhost:3000 it redirects to https://localhost:3000 which is correct, however it will complain about missing SSL certification.. SSL connection error Unable to make a secure connection to the server. This may be a

Ruby on rails: force_ssl not redirecting from http to https when using thin start --ssl

你。 提交于 2019-12-01 23:15:50
I have been trying to configure my rails project to use SSL (as application wide) with thin (by adding thin gem and placing config.force_ssl = true to application.rb ) but as a result, I have an annoying problem. When I start my rails server using rails s and try to access http://localhost:3000 it redirects to https://localhost:3000 which is correct, however it will complain about missing SSL certification.. SSL connection error Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have

Chrome asks to “Select a Certificate” for SSL on my Rails app using thin

笑着哭i 提交于 2019-12-01 20:02:05
I have a Rails app that is configured to only use SSL. I also have free SSL certificates from StartSSL. I use thin as my web server with this command: thin start -p 80 & thin start -p 443 --ssl --ssl-key-file ./.ssl/sslkey.key --ssl-cert-file ./.ssl/sslcert.cert & This technically works-- visiting the http version of my site redirects to the https version. However, Chrome and Safari both prompt me when I visit the site to "Select a Certificate" from my local Keychain to validate with the server. This behavior is not desirable. How do I set up thin with SSL in such a way that this dialog does

Chrome asks to “Select a Certificate” for SSL on my Rails app using thin

帅比萌擦擦* 提交于 2019-12-01 17:27:19
问题 I have a Rails app that is configured to only use SSL. I also have free SSL certificates from StartSSL. I use thin as my web server with this command: thin start -p 80 & thin start -p 443 --ssl --ssl-key-file ./.ssl/sslkey.key --ssl-cert-file ./.ssl/sslcert.cert & This technically works-- visiting the http version of my site redirects to the https version. However, Chrome and Safari both prompt me when I visit the site to "Select a Certificate" from my local Keychain to validate with the

Why do we need nginx with thin on production setup?

安稳与你 提交于 2019-12-01 14:35:57
问题 Why do we need to install nginx with thin on production setup, As thin is itself a web server. Every blog post people are using ruby+rails+nginx+thin? 回答1: As stated by Michael nginx balances thin (whatever that means). But another reason to use nginx in front of any ruby server is to serve static files (if you use page caching, they also can be served by nginx), which means requests wont even touch your ruby app, and increase a lot your performance. Also nginx although it seems to be the

Problems installing Thin on windows 7 x86

我怕爱的太早我们不能终老 提交于 2019-12-01 11:43:28
问题 I'm having problems getting thin working on my Windows 7 machine (I've already installed eventmachine v0.8.1): > gem install thin --ignore-dependencies checking for main() in -lc... no creating Makefile make 'make' is not recognized as an internal or external command, operable program or batch file. Are there not meant to be precompiled binaries available for thin? 回答1: Apparently, there aren't any pre-built binaries. You will need a C compiler installed. If you installed Ruby via the

Rails 3.2 Asset Pipeline with Thin and Apache, not finding assets

安稳与你 提交于 2019-12-01 03:28:21
My question is similar to this one Rails 3.2 Asset Pipeline with Passenger Endless Errors except that when I try to actually go to <link href="/assets/application-eed7996ee9017637f923133371ab3e92.css" media="all" rel="stylesheet" type="text/css" /> I get a 404. Here's the thing I don't understand. It is looking in /assets/, but when I look at the code that was deployed, the assets are only in /public/assets, which is actually a symlink to /var/www/myapp/shared/assets. So what in the world is responsible for telling the app that looking in /assets will produce correct results?? I am using Rails

Rails 3.2 Asset Pipeline with Thin and Apache, not finding assets

醉酒当歌 提交于 2019-12-01 00:21:19
问题 My question is similar to this one Rails 3.2 Asset Pipeline with Passenger Endless Errors except that when I try to actually go to <link href="/assets/application-eed7996ee9017637f923133371ab3e92.css" media="all" rel="stylesheet" type="text/css" /> I get a 404. Here's the thing I don't understand. It is looking in /assets/, but when I look at the code that was deployed, the assets are only in /public/assets, which is actually a symlink to /var/www/myapp/shared/assets. So what in the world is