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 end I used a model where Capistrano would use a consistent
location to
deploy to, and Apache would link back into that structure ...
e.g.
set :deploy_to, "/sw/#{application}/current/public/#{realm}/" #
realm = (QA,DEV,PRD, etc)
desc "Install Apache"
task :install_apache, :roles => :apache do
link_cmd1 = "ln -s #{:deploy_to }/Apache /usr/local/apache/conf"
link_cmd2 = "ln -s #{:deploy_to }/Apache /usr/local/apache/htdocs"
run link_cmd1
run link_cmd2
end
Peter
PS - seekingalpha.com - great name, great site - is it rails based?
On Apr 1, 2007, at 2:11 PM, Rob Sanheim wrote:
>
> 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 like is the standard deploy/rollback
> functionality: so export/co to a timestamped dir, symlink that to a
> 'current' somewhere (which is where Apache/nginix/whatever is
> watching), and then reload the server. If this could be done with the
> builtin in tasks, then we could get things like rollback for free.
>
> Is this possible, or are the current baked in depoy tasks too coupled
> to Rails for it to work?
>
> - Rob
>
> http://robsanheim.com
> http://seekingalpha.com
>
> >
Peter Booth
[EMAIL PROTECTED]
917 445 5663
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
