Azure-App-Service / ruby

Apache License 2.0
22 stars 20 forks source link

Startup Command not working #44

Open antarr opened 3 years ago

antarr commented 3 years ago

I'm trying to use the startup command to run a Procfile so that my delayed_job workers are loaded. I've changed the startup command to foreman start and the server starts fine but the workers do not. I'm not getting any errors but none of my jobs are ever executed.

Procfile

web: bundle exec rails s -p $PORT
worker: bundle exec rake jobs:work
dombarnes commented 3 years ago

You'll be better to roll your own Docker setup for this, that way you can run a multi container setup with a docker-file, one to run your rails app and one to run your active job runner. I do this with sidekiq