2008/4/25 Rafael G. [EMAIL PROTECTED]:
Josh Schairbaum escribió:
You can set the number of releases to keep, but you'll have to look in
the docs for the variable name, I can't remember.
I remember :)
set :keep_releases, 4
regards!
As an aside, does anyone else notice
CapGun has been updated to 0.0.2. CapGun is a super simple deployment
notifications for Capistrano.
Changes in this version: converts the release times to the current
time zone; improved docs.
More info:
* Log bugs, issues, and suggestions on Trac:
Tell everyone about your releases! Send email notification after
Capistrano deployments! Rule the world!
Drop your ActionMailer configuration information into your deploy.rb
file, configure recipients for the deployment notifications, and setup
the callback task.
Setup and configuration are
On 5/11/07, Jamis Buck [EMAIL PROTECTED] wrote:
Rob,
Yeah, that's been possible since Preview 1, actually:
run cp $CAPISTRANO:HOST$.conf /etc/httpd/vhosts.d
The $CAPISTRANO:HOST$ string will be replaced by the actual hostname,
immediately before executing the command.
- Jamis
I
Is there a way to do before/after tasks for any task? So a sort of
catch all callback task? Basically before_any/after_any...
- rob
--
http://robsanheim.com
http://seekingalpha.com
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL
I know this is probably wishful thinking, but I'd love to do this:
set :my_func, lambda { my_method }
then
task :after_deploy do
where my_method is just some ruby code in a custom task.
--
http://robsanheim.com
http://seekingalpha.com
--~--~-~--~~~---~--~~
Sorry, sent that too early. I'd like:
set :my_func, lambda { # arbitrary ruby code here }
then
task :after_deploy do
my_func # this runs the lambda in the context of all servers for
this task, not locally
end
The reason I ask for this is because I find myself writing a lot of
little helper
On 4/4/07, goodieboy [EMAIL PROTECTED] wrote:
Hi,
The application I'm setting up is running everything local. And
actually, there is no database. We're using Solr for that.
Is it still possible to use Capistrano for deployment?
Thanks
Yes, and it would still be a good idea to use
Does anyone have any ideas on how to test capistrano custom tasks?
Just call them from a normal unit test via a system call, and assert
the results?
- Rob
--
http://robsanheim.com
http://seekingalpha.com
--~--~-~--~~~---~--~~
To unsubscribe from this group,
HI all
Has anyone moved their config files to be managed by capistrano,
particularly web server stuff? The number of machine we have to
manage is growing all the time, so it would be great if we could use
the same deployment procedure with config stuff as we do with Rails.
The main things I'd
On 4/1/07, Peter Booth [EMAIL PROTECTED] wrote:
I tried using Capistrano to deploy Apache and Tomcat content and
config files.
It worked fine, once I fixed some permissions problems. The toolset
was fine,
the hard part was thinking through the design of what gets deployed
where.
In the
How does everyone handle security so they can do one step deploys?
For instance, right now the user we use for our deployments doesn't
have password-less sudo rights, so I still have to enter a password
for the mongrel restart. When I'm deploying many times a day (for
example - to our staging
Jamis could you push a new version of Capistrano soon? I really want
that new 'get' functionality, and don't want to try and manage a trunk
version on all of our servers where we need it.
- Rob
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to
On 1/23/07, NeilW [EMAIL PROTECTED] wrote:
Ezra,
I appreciate that the method_missing idea has a certain appeal to it,
but does it really save that much time for the aggravation it might
cause?
I don't see a vast saving between
sh.rm_rf fred
and
sh.rm -rf fred
Particularly when
I'd like to keep everything in svn, including any maintenance files
under /system. Is this possible with Capistrano?
thx,
- Rob
--~--~-~--~~~---~--~~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
On 12/23/06, Jamis Buck [EMAIL PROTECTED] wrote:
Here it is, Capistrano 1.3.0. Mostly it is just bug fixes, but it
includes a few minor new features.
The new features:
* The sudo() method now supports an :as option, so that you can
specify who the command should be executed as. This defaults
16 matches
Mail list logo
