puma

问题 This might be a two-in-one question. I have a Rails application for home/hobby usage, hosted on a Raspberry Pi and I was wondering if it's possible to create a local SSL certificate for it and setup Rails to use it? If yes, how can I setup my Rails/Puma/Foreman/Ubuntu application? For now, I am running the application with Foreman, by using a Procfile: web: bundle exec puma -t 8:8 -p 3000 worker: bundle exec sidekiq clock: bundle exec clockwork config/clock.rb 回答1: Yes you can. Here is a gist

问题 This might be a two-in-one question. I have a Rails application for home/hobby usage, hosted on a Raspberry Pi and I was wondering if it's possible to create a local SSL certificate for it and setup Rails to use it? If yes, how can I setup my Rails/Puma/Foreman/Ubuntu application? For now, I am running the application with Foreman, by using a Procfile: web: bundle exec puma -t 8:8 -p 3000 worker: bundle exec sidekiq clock: bundle exec clockwork config/clock.rb 回答1: Yes you can. Here is a gist

问题 Tried installing Puma on Windows and getting this error - Temporarily enhancing PATH to include DevKit... Building native extensions with: '--with-opt-dir=c:\openssl' This could take a while... ERROR: Error installing puma: ERROR: Failed to build gem native extension. C:/RailsInstaller/Ruby2.1.0/bin/ruby.exe extconf.rb --with-opt-dir=c:\openssl checking for BIO_read() in -lcrypto... no checking for BIO_read() in -llibeay32... no *** extconf.rb failed *** Could not create Makefile due to some

问题 I am trying to deploy Rails app with the Puma web server. When trying to start Puma server with a config file bundle exec puma -C config/puma.rb I get an error that the address is already in use. Does someone know how to fix this? bundle exec puma -C config/puma.rb [23699] Puma starting in cluster mode... [23699] * Version 2.11.3 (ruby 2.0.0-p353), codename: Intrepid Squirrel [23699] * Min threads: 5, max threads: 5 [23699] * Environment: development [23699] * Process workers: 2 [23699] *

问题 I'm trying to install the puma gem, but when I run gem install puma I get this error message: Temporarily enhancing PATH to include DevKit Building native extensions. This could take a while... ERROR: Error installing puma: ERROR: Failed to build gem native extension. C:/Ruby193/bin/ruby.exe extconf.rb creating Makefile make generating puma_http11-i386-mingw32.def compiling http11_parser.c ext/http11/http11_parser.rl: In function 'puma_parser_execute': ext/http11/http11_parser.rl:111:3:

问题 Hello I am trying to share a unix socket from my docker container rails app to my ubuntu host in order to connect puma server with nginx reverse proxy. In my docker-compose file I have: version: '3.2' services: web: command: puma -b 'unix:///var/run/puma.sock?umask=0777' ports: - '3000:3000' volumes: - /var/run/puma.sock:/var/run/puma.sock:rw I am getting this error on web service when loading with volumes: web_1 | * Listening on unix:///var/run/puma.sock?umask=0777 web_1 | /usr/local/bundle

问题 I created free account on heroku. Now I am trying this getting started. My DevKit Ruby and openssl are placed inside my D:\ disk, not C:\ , beacuse there is reason why I can't use C:\ disk. All files directories are placed in my path. I have tried to install puma gem by this method, only defference is that disk name is D:\ . When I run gem install puma -- --with-opt-dir=D:\openssl it throws me an long error: D:\>gem install puma -- --with-opt-dir=D:\openssl Building native extensions with: '-

问题 The deployment was successful and everything is green. But when we try to access the application URL, it gives 502 Bad Gateway error. Checking for puma process with ps -aux | grep puma doesn't return any process attached to puma server but pgrep returns following. $pgrep -fl puma 18009 su -s /bin/bash -c bundle exec puma -C /opt/elasticbeanstalk/support/conf/pumaconf.rb webapp 18031 ruby /opt/rubies/ruby-2.0.0-p598/bin/puma -C /opt/elasticbeanstalk/support/conf/pumaconf.rb 回答1: I have tried

问题 I am using rails + puma as my production server. I used httpd to set up virtual machine and forward request to localhost:3000. And the command I used to start up my puma server is(inside the app folder already) puma -e production -p 3000 & Everything with my web app is fine when I was still logged in the server with ssh. only that some logs actually appears on the screen(I did not pay attention to it). However, when I exited the ssh session. I cannot use omniauth(a gem). I looked inside the

问题 Hi i followed this thread of digitalocean to deploy my RubyOnRails app on digitalocean vps https://www.digitalocean.com/community/tutorials/how-to-deploy-a-rails-app-with-puma-and-nginx-on-ubuntu-14-04 My Config: 512 MB RAM(with 1 gb swap) ubuntu 16.04 Ruby2.33(with rbenv) This tutorial lists usage of upstart but as i searched i found ubuntu 16.04 uses systemd. I found this thread but still could start Puma Server https://github.com/puma/puma/issues/1211 when i run which puma it gives /home