new mongrels
|
|
I’ve upgraded my brightbox recently and now like to add more mongrel servers. I’ve outcommented the line ‘set :mongrel_servers, 2’ and changed it to 4, run cap deploy:setup and then cap:deploy afterwards but it still only shows two mongrels starting. cheers for any pointers |
|
|
Hi Volker. If you change the number of mongrels you’ll need to run “cap deploy:initial” again. This is the task that does the initial setup of mongrels and the Apache configuration. |
|
|
is there a way to do it without running migrations? |
|
|
Volker. It shouldn’t matter – migrations that have already been run won’t run again. Otherwise, I’m not sure how you’d stop them running, you could dig into the source of the brightbox gem and try commenting out the part that runs migrations. We’re working on a new version of the gem and every report like this is very useful for us to plan what extra features need adding. |
|
|
the problem is that i stopped using migrations for a while as it was simply to linear for development purposes. Would it be sufficient to set the version in schema info higher than the latest migration to prevent it from running? Volker |
|
|
You can safely run deploy:initial without losing data. I assume you’re using the local or global shared_dirs or shared_files system that our gem provides. |
|
|
thanks for the help I’ll give it a go. Volker |
|
|
I’ve tried to run deploy:initial and get the following error message: |
|
|
Hi Volker, It sounds like you don’t have rubygems and/or the brightbox-server-tools package – try a ‘sudo apt-get install rubygems’ and a ‘sudo gem install brightbox-server-tools’. |
|
|
thanks, that was the problem. brightbox gem mismatch. |
|
|
Hi Volker, The gem is actually configured for a standard rails app deployment. We do the kind of configuration you talk about ourselves sometimes for our internal projects and it does always have to be done by hand. |
|
|
Hello David. thanks for the answer. When the time comes I’ll post a support ticket if I need help. Volker |