Ticket #40 (closed defect: fixed)

Opened 10 months ago

Last modified 10 months ago

install_rails_stack inappropriately requires :application to be defined

Reported by: zippy Assigned to: somebody
Priority: major Milestone:
Component: component1 Version:
Keywords: Cc:

Description

Working my way through using deprec2 to handle setting up a server that runs a couple different apps, I've come across this:

The suggestion in the README.slicehost of setting up a "sys" project to set up the server is great, but it fails if you try to run install_rails_stack from that directory because of the mongrel:install task. The issue is that the task assumes that you've set up the application name to be used as part of mongrel_user_prefix in create_mongrel_user_and_group. This assumption isn't good for a "sys" project where a machine that may be running several apps is being set up prior to setting up the apps. I didn't touch :application in the deploy.rb created by the original capify so install_rails_stack ended up trying to run this:

  • executing "sudo -p 'sudo password: ' grep 'app_set your application

name here:' /etc/group sudo /usr/sbin/groupadd app_set your application name here"

:-)

Would it make sense to mov #create_mongrel_user_and_group to #config_project ?

Change History

01/31/08 03:14:53 changed by zippy

The converse situation is true too. When you do a deploy:setup after having done an install_rails_stack it asks you if you want to overwrite the configuration files just created. This is weird...

02/01/08 00:46:38 changed by mbailey

  • status changed from new to closed.
  • resolution set to fixed.

I moved create_mongrel_user_and_group to config_project

I also updated deploy:setup to call deprec:mongrel:config_project instead of deprec:mongrel:config so it won't prompt about over writing the system config files for mongrel.