Hi Roberto:
>
> 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.
***deploy.rb***
require 'mongrel_cluster/recipes'
role :web, "10.0.1.5"
role :app, "10.0.1.5"
role :db, "10.0.1.5", :primary => true
set :application, "animal_shelter"
set :deploy_to, "/var/apps/#{application}" # /var/apps/ is owned by
deploy
set :user, "deploy"
set :repository, "your_repository_here"
set :use_sudo, false
*** server ***
No configuration needed.
*** dev machine ***
First deployment:
cap -a setup
cap -a configure_mongrel_cluster
cap -a cold_deploy
Subsequent deployments:
svn commit -m "more software"
cap -a deploy
> 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".
>
By default the config file is written to deploy_to/config. It looks
like your deploy_to variable contains "current" as
configure_mongrel_cluster writes to deploy_to/config/
mongrel_cluster.yml. deploy_to should be the root directory of your
deployment.
Feel free to send me a censored version of your deploy.rb and I'll
talk a look for anything unusual.
Thanks,
Bradley
------
Rails Machine
Simplified Ruby on Rails application deployment
http://railsmachine.com
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
