I posted this to the rails list before by mistake, and only later realized that there is a specific mongrel list.

Uff, I got lost. I had mongrel_cluster 0.1working fine, even with capistrano (my own hack). Then came  mongrel_cluster 0.1.1 and  I tried to set it up, but somehow I messed up things and nothing worked anymore. So here is what I did:


on production machine:  (debian linux, rails 1.1)
------------------------------
- installing  mongrel_cluster 0.1.1


on development machine: (windows XP, raills 1.1)
-----------------------------------------------------------------------
- inststalling mongrel_cluster 0.1.1

- recreating config file: mongrel_rails cluster::configure

- modifying configfile manually to make it look like this: (will be more the one server later)
---
num-procs: 1024
docroot: public
timeout: 120
cwd: /home/me/sites/myapp/current
log_file: log/mongrel.log
port: 3000
config_script:
debug: false
environment: production
servers: 1
pid_file: log/mongrel.pid
address: 0.0.0.0
mime_map:

- deploy.rb: commented out my old restart and spinner tasks and added: require 'mongrel_cluster/recipes'

- deployment: rake deploy   (fails because config file is at: /home/me/sites/myapp/current/config/mongrel_cluster.yml)
...
executing "mongrel_rails cluster::restart -C /home/me/sites/myapp/config/mongrel_cluster.yml"
...


then I thought I could give "cap -a configure_mongrel_cluster" a try, hoping it would put things into the right order, but I got this:

 ** [out :: xx.xx.xx.xx] !!! Path to log file not valid: log/mongrel.log
 ** [out :: xx.xx.xx.xx] cluster::configure reported an error. Use -h to get help.



So what is wrong with the way  I approached  capistrano mongrel_cluster ?

regards
--
Roberto Saccon
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to