foreman

On my local machine I'm trying to start my rails app and delayed job worker using Foreman. My Procfile looks like this: web: bundle exec rails server -p $PORT worker: bundle exec rake jobs:work When I start foreman only the first two web requests get executed. With the third request the server hangs. The first request is outputted in the console, the second isn't. If I leave out the worker in my Procfile the server is running just fine and is outputting everything to the console. Also when I start the rails server and worker without Foreman everything is working fine. So it looks like there's

I installed redis this afternoon and it caused a few errors, so I uninstalled it but this error is persisting when I launch the app with foreman start . Any ideas on a fix? foreman start 22:46:26 web.1 | started with pid 1727 22:46:26 web.1 | 2013-05-25 22:46:26 [1727] [INFO] Starting gunicorn 0.17.4 22:46:26 web.1 | 2013-05-25 22:46:26 [1727] [ERROR] Connection in use: ('0.0.0.0', 5000) Check your processes. You may have had an unclean exit, leaving a zombie'd process behind that's still running. Just type sudo fuser -k 5000/tcp .This will kill all process associated with port 5000 This

I have a sinatra app in which i have a yml file to set environment variables, i call them using this method module MyConfig def config environment = ENV["RACK_ENV"] || "development" YAML.load_file("./config/config.yml")[environment] end end so when i want to use a variable i do this for example aws_access_key_id = config['aws_access_key'] I have a .gitignore file that ignores config.yml when pushing to github for example.So when I push to heroku these environment variables will not be accessible? So this leaves me with using the heroku way of setting them like so heroku config:add aws_access

I want the foreman gem to use the PORT value provided in the my development env file instead of using its own values. My files setup is shown below: A bash script to start foreman: foreman start -e development.env The development.env file content: PORT=3000 The Procfile content web: bundle exec rails server thin -p $PORT -e $RAILS_ENV $1 The dev server ends up starting on port 5000. I know I can start foreman with --p 3000 to force it to use that port. But that defeats the purpose of the env file. Any suggestions? Looking at the code: https://github.com/ddollar/foreman/blob/master/lib/foreman

I am trying to export my application to another process management format/system (specifically, upstart ). In doing so, I have come across a number of roadblocks, mostly due to lacking documentation. As a non-root user, I ran the following command (as shown here ): -bash> foreman export upstart /etc/init ERROR: Could not create: /etc/init I "could not create" the directory due to inadequate permissions, so I used sudo : -bash> sudo foreman export upstart /etc/init Password: ERROR: Could not chown /var/log/app to app I "could not chown... to app" because there is no user named app . Where is

I just got into rails programming and it looks like there are two programs I can use to run my project locally: rackup and foreman. One difference I noticed is that foreman will not output some things that I would expect to see and I would see if I ran rackup instead, until I press ctrl+c to close the server. Then all those messages appear, as if they were being hidden. Is there a reason for this? How can I get foreman to be more verbose? If you are not seeing any output from your program, there is a likely chance that it is buffering stdout. Ruby buffers stdout by default. you can fix this by

I can run guard from within my foreman procfile - but the output is not as colorful as I'd like. The only color I see in my output is from Foreman... I want to have a guardfile that manages rspec, cucumber and jasmine - AND have that nice color output when those tests run. It would seem as if foreman ignores guard file settings. Any idea how to change that? Add the --tty option to your rspec guard cli: guard "rspec", :version => 2, :cli => "--tty ...other options..." For version 4.5.0 of guard-rspec the following worked for me guard :rspec, cmd_additional_args: "--tty", cmd: ...other... EDIT: