puma

Heroku Open “Puma Port 5000 Already In Use” Rails

由 半城伤御伤魂 提交于 2019-12-10 23:33:36
问题 When I Control-C to quit "Heroku Open" (the Heroku Toolbar server command). I'm unable to restart. I receive this error: /vendor/bundle/gems/puma-2.14.0/lib/puma/binder.rb:233:in `initialize': Address already in use - bind(2) for "0.0.0.0" port 5000 (Errno::EADDRINUSE) web.1 | s/vendor/bundle/gems/puma-2.14.0/lib/puma/cluster.rb:304:in `run' Is their a "correct" way to shut down the Heroku Toolbar local rails server in order to avoid this problem? 回答1: The only method I've used that works to

Can a Rails 5 application with ActionCable be deployed on Windows?

由 微笑、不失礼 提交于 2019-12-10 23:21:56
问题 I have a Rails 5 application which I was planning to deploy on Linux, but because we needed some access very specific Windows-only software, I need to deploy it on Windows Server 2012 R2. My software stack (or mix) was supposed to be Nginx/Puma/Rails/PostgreSQL/Redis. Everything installs for me on Windows except Puma, and the Rails documentation says that I need Puma for ActionCable. How do I get Puma to run on Windows? I have seen and tried snippets of things to try, and I have also seen and

Windows puma unable to load application due to backports Bad File descriptor

由 删除回忆录丶 提交于 2019-12-10 22:48:12
问题 I'm trying to run a puma project on my Windows 8 machine and keep getting this error whenever I try to run bundle puma exec -p 4567 I get an error about a Bad file descriptor in part of the backports code. PS C:\Users\andrew\work\test> bundle exec puma -p 4567 DL is deprecated, please use Fiddle *** SIGUSR2 not implemented, signal based restart unavailable! *** SIGUSR1 not implemented, signal based restart unavailable! *** SIGHUP not implemented, signal based logs reopening unavailable! Puma

`rails server` using Puma and domain name pointing to 127.0.0.1

由 混江龙づ霸主 提交于 2019-12-10 21:15:42
问题 I have a Rails application that uses subdomains (legacy application, I've been wanting to change that, not yet). I deployed my app to Heroku and I've started to test Puma because it's the recommended choice for Heroku and the default in the upcoming release of Rails. When I used WEBrick (locally) I was able to test my subdomains using a DNS record that pointed to 127.0.0.1 such as vcap.me, specifically http://vcap.me:3000/ would point to my app and http://abcde.vcap.me:3000/ will correctly

Right way to deploy Rails + Puma + Postgres app to Elastic beanstalk?

由 戏子无情 提交于 2019-12-10 04:13:29
问题 I have an Rails 5 API which I am trying to deploy(correctly) on Elastic Beanstalk. Here is my initial config/puma.rb file which I use: threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }.to_i threads threads_count, threads_count # Specifies the `port` that Puma will listen on to receive requests, default is 3000. port ENV.fetch("PORT") { 3000 } # Specifies the `environment` that Puma will run in. environment ENV.fetch("RAILS_ENV") { "development" } # Allow puma to be restarted by `rails

Error while starting Puma server with workers

由 痴心易碎 提交于 2019-12-09 09:18:26
问题 I am new to Rails and Puma, so the issue might be too silly with simple solutions, also please guide me if you think i am doing something wrong. I am trying to start the Puma server for my rails with the worker. If i set workers to 0 with puma -w0 the server starts perfectly but if i set worker to 1 or more it gives the following error: E:\RoR_tryouts\ws_13.11.13\todo>puma -w3 [2120] *** SIGUSR2 not implemented, signal based restart unavailable! [2120] *** SIGUSR1 not implemented, signal

Puma Stops Running for Rails App on EC2 Instance with Nginx (using Capistrano/Capistrano Puma)

由 ♀尐吖头ヾ 提交于 2019-12-08 07:54:08
问题 My top-level question is, how can I get Puma to stop failing. But that is really made up of lots of smaller questions. I will number and bold each of them, to try to make this question answerable. I am hosting a Rails application on an EC2 instance that is a t2.nano. This is admittedly, a very small box--but I don't expect my website to receive any traffic. I configured everything successfully with Nginx and Puma using Capistrano and Capistrano Puma. Everything was great, until one day I went

error with puma in local server

由 让人想犯罪 __ 提交于 2019-12-08 07:37:43
问题 I recently added puma to my app for better performance on heroku. my app works well in production (live) environment but I am getting and error in my local environment.. error when I try to start my server: Art West@ARTWESTIV ~/desktop/drinkPGH (master) $ rails s => Booting Puma => Rails 4.1.8 application starting in development on http://0.0.0.0:3000 => Run `rails server -h` for more startup options => Notice: server is listening on all interfaces (0.0.0.0). Consider using 127.0.0.1 (-

Puma - Rails on linux // Restart when process dies

由 时间秒杀一切 提交于 2019-12-07 17:54:53
问题 Using puma on a rails app; it sometimes dies without any articular reason; also often dies (does not restart after being stopped) when deployed What would be a good way to monitor if the process died, and restart it right way ? Being called within a rails app; I'd be useful to have a way to defines it for any apps. I did not found any useable ways to do it (looked into systemd, other linux daemons… no success) Thanks if any feedback 回答1: You can use puma control to start/stop puma server. If

Puma Stops Running for Rails App on EC2 Instance with Nginx (using Capistrano/Capistrano Puma)

由 ╄→гoц情女王★ 提交于 2019-12-07 16:03:27
My top-level question is, how can I get Puma to stop failing. But that is really made up of lots of smaller questions. I will number and bold each of them, to try to make this question answerable. I am hosting a Rails application on an EC2 instance that is a t2.nano. This is admittedly, a very small box--but I don't expect my website to receive any traffic. I configured everything successfully with Nginx and Puma using Capistrano and Capistrano Puma. Everything was great, until one day I went to my website and saw the Nginx 504 message. I opened the Nginx error log and saw that it could not
订阅 puma