Another option, if it is just a single file; you can declare declare
the server in question to be :no_release => true, and then just use
put to upload the file to wherever you need it:
# :no_release => true prevents the app from being deployed to this
server
role :other, "this.little.server", :no_release => true
task :copy_the_file, :roles => :other do
put File.read("/local/path/to/file"), "/remote/path/to/file"
end
after "deploy:update_code", :copy_the_file
A drawback here is that you lose the ability to rollback to a
previously deployed copy of that file, unless you manually track
versions and do the symlink hokey-pokey and so forth.
- Jamis
On Jun 14, 2007, at 7:16 AM, Wayne E. Seguin wrote:
>
> Sascha,
>
> I have a similar situation as I use Cap2 to deploy configurations to
> various servers, each server gets different configurations.
>
> My suggestion:
>
> Make a custom deployment task that sets the :repository url to be
> checked out to be right to that file.
> In the custom task you'll have to redefine role :app to point to the
> server in question and adjust any other settings as needed.
> That way it will checkout that file only to the server in question.
>
> On 13 Jun, 15:55, Sascha Koni <[EMAIL PROTECTED]> wrote:
>> I would prefer to just upload the one file. I don't think all the
>> other rails stuff has anything to do on that other server.
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
