Hi Julien,
AP4R has its own Capistrano recipe in lib/ap4r/recipe.rb from ver.0.3.4.
It can handle just one AP4R process per server now,
and defines deploy, (re)start, start, update and some more tasks in namespace
:ap4r .
The recipe is probably applicable to versions >= 0.3.2.
It will (may?) goes well as
1. Run "capify ." in your AP4R's working directory (which has config, script,
and some directories)
2. Sample deploy.rb file is as follows:
===== BEGIN =====
require 'ap4r/recipes'
set :application, "trunk_test"
set :repository, "SET_YOUR_REPO_PATH/#{application}"
set :deploy_to, "/SOMEWHERE_YOU_WANT/#{application}"
set :ap4r_conf, "#{current_path}/config/queues_your_config.cfg"
role :ap4r, "10.18.0.25"
===== END ======
I'm sorry that I don't explain exactly. I don't have much time now :-<
Please let me know any comments or feedbacks!
P.S.
Handling more than one AP4R processes is in my TODO list.
So some configuration parameter may be changed in future release.
Regards,
shino
> -----Original Message-----
> >> As most of you, I am using Capistrano to deploy my app. Everything is
> >> going smoothly for my app itself, but I would really love to automate
> >> the deployment of AP4R at the same time, whether it's on the same
> >> server or on another one. Anyone has some tips? or has ever done
> >> this?
_______________________________________________
ap4r-user mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ap4r-user
