ok, I uninstalled 0.1 to make absolutely sure that 0.1.1 is running and did all configuration steps again and now it even got worse: after deploying the "current" symlink points to a nonexistent "config".

Bradley, can you show a simple, but working example of what needs to be configured at the develpment machine and what needs to be done at the production machine (if anything at all)  ? Then I hopefullyI  can figure out what I am doing wrong.

On 5/4/06, bradley taylor <[EMAIL PROTECTED]> wrote:
Hi Robert:


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.

This was a problem with 0.1, but should be resolved in 0.1.1.

I  changed cluster::configure to not validate log paths.  Double check the version with " gem list mongrel_cluster" please.

Thanks,
Bradley

------
Rails Machine
Simplified Ruby on Rails application deployment





_______________________________________________
Mongrel-users mailing list
Mongrel[EMAIL PROTECTED]
http://rubyforge.org/mailman/listinfo/ mongrel-users




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

Reply via email to