sidekiq

I am using rails, sidekiq and docker. My docker-compose.yml file sidekiq: build: . command: bundle exec sidekiq -C config/sidekiq.yml links: - db - redis config/sidekiq.yml file :pidfile: ./tmp/pids/sidekiq.pid :logfile: ./log/sidekiq.log :queues: - default After I run docker-compose up , the sidekiq service can not start rightly. sidekiq_1 | No such file or directory @ rb_sysopen - /testapp/tmp/pids/sidekiq.pid sidekiq_1 | /usr/local/bundle/gems/sidekiq-3.5.3/lib/sidekiq/cli.rb:365:in `initialize' sidekiq_1 | /usr/local/bundle/gems/sidekiq-3.5.3/lib/sidekiq/cli.rb:365:in `open' sidekiq_1 |

How can I run sidekiq as daemon on Ubuntu? If I run bundle exec sidekiq -D I get invalid option: -D , is there any way to run it without some other controller, like god, upstart...? there's an option to Daemonize sidekiq, just pass -d option commit Running as daemon won't restart the sidekiq if it crashes unexpectedly. One alternate way could be to run sidekiq as a service (An upstart job). If the system is rebooted than also the upstart job will run sidekiq. Here is the complete script and method to run sidekiq as a service. After running sidekiq as a service you can simply start/stop/restart

I came across following method in sidekiq gem . Its just invoked from test_sidekiq.rb . def self.❨╯°□°❩╯︵┻━┻ puts "Calm down, bro" end This is the only link I was able to find on SO. Google can't understand ❨╯°□°❩╯︵┻━┻ . Why doesn't Ruby complain about this encoding? What is the purpose of this method (not much looking at its body)? Why did author @mike-perham use this name? Just for fun, or testing some boundaries? If you really do not understand the sense of the method name, that is a (Japanese-style) facemark. Whereas English facemarks are rotated 90 degrees counter-clockwise and are long

I just recently install GitLab v5.0 on an Ubuntu 12.04 server and am now having issues with email notifications. I can't get GitLab to send any emails of any kind. I've got my config/environments/production.rb file setup to use sendmail as the transport service: config.action_mailer.delivery_method = :sendmail config.action_mailer.perform_deliveries = true config.action_mailer.raise_delivery_errors = true And I can manually use sendmail successfully from the shell as described here: http://scratching.psybermonkey.net/2011/03/sendmail-how-to-test-sending-email.html My config/gitlab.yml file is

I'm using a Sidekiq worker to complete some requests to Facebook after a user signs-in for the first time. Typically the task takes around 20 seconds or so. I'd like to load some information on to the page using an ajax request as soon as the sync is completed, but am unsure as to the best way to check for the job completion with Javascript. One possibility would be to configure the Sidekiq worker to set a cookie after the rest of the jobs are done. Then I can use a setTimeout function to keep checking for the cookie before calling the load function. But I'm unsure whether this is the best way

I have Unicorn, Sidekiq and Postgres setup. I am trying to understand the right configuration to set up so that I don't hit the maximum db connection limit. In Opsworks, the m1.small Postgres RDS instance can have a max of 121 connections. I have a db pool size of 5. Consider this. Sidekiq and Unicorn are its own process. So the db pool size for each process is 5. Correct me if my understanding here is wrong. If I have 5 unicorn process', that means 5*5=25 database connections Now this is the part where I am slightly confused, since Sidekiq is multithreaded. If Sidekiq has a concurrency of 5.

I am using sidekiq gem to run API calls in background. I ran sidekiq in Daemon process like: bundle exec sidekiq -d Now I made some changes in my method, so I want to restart sidekiq. I tried to kill the sidekiq by using the below command: kill -9 process_id but it's not working. I want to know the command to restart sidekiq process. If you have any idea please share with me. I tried the below command also: sidekiqctl stop /path/to/pid file/pids/sidekiq.pid So after you find you proces_id, use the below command, that will stop the workers from getting new jobs, and they will finish existing