Bug #861
closedforeman shows blank page on initial startup from non web-brick start
Description
I added an apache vhost for foreman and then started httpd. When I went to http://foreman:3000 I only received a blank page. I figured something hadn't triggered so I stopped httpd. I then fired up foreman via script/server -e production in order to initialize the database that was empty. Once I saw the foreman homepage I stopped the web brick server and restarted httpd. Everything works as expected via apache now after initializing via web brick.
Maybe it has something to do with the -e production being available in apache?
Updated by Corey Osman about 13 years ago
Maybe it has something to do with the -e production being available in apache?
should be
Maybe it has something to do with the -e production NOT being available in apache?
Updated by Ohad Levy about 13 years ago
- Status changed from New to Feedback
how are you using it?
the best way would be to use something such as passenger(see example puppet module for foreman), my guess is that your apache instance has no access to your db.