I don't find it clean like that.
For myself, I do one folder by application. Each one are capified and have
their own deploy.rb file.
If you need code that you want to use in all those application's deploy.rb file,
I would do it in a separate file let's say deploy_base.rb and including it in
each deploy.rb file.
So you could have
applications/
app1/
config/
deploy.rb
...
app2/
config/
deploy.rb
...
deploy_base.rb
-- Philippe Rathé
On 2011-09-18, at 11:10, grant wrote:
> I don't have specifics here, but my task goes something like this:
>
> task deploy_app1_ do
> `git clone ...` # get latest first as neither the hosts or master
> have access to repository
> set scm:none
> set deploy_to : '/target/dir'
> set deploy_via: copy
> set shared_dir: 'other/dir'
> deploy.update #calling update rather than deploy as I just need
> files copied and symlink updated
> end
>
> the deploy.rb has other non-changing properties set, and creates a
> role for the hosts that are currently available. In our situation the
> hosts are not always available as they are on our clients' networks.
>
> These properties would change with deploy_app2 task to deploy another
> app. I'm just wondering if there is a better approach, like creating
> separate Cap files for each project and/or using railsless/deploy?
> The multiple task option has worked in our test environment.
>
>
> If you need more details with actual code I can send tomorrow from
> work.
>
> Thanks again,
>
> grant
> I'm wondering if this is a feasible approach
>
> On Sep 17, 5:45 pm, prathe <[email protected]> wrote:
>> Grant,
>>
>> can you provide an example?
>>
>> On 2011-09-17, at 16:01, grant wrote:> Hi,
>>
>>> I've made some progress using different tasks to deploy different, non-
>>> rails projects by setting some properties, like scm, deploy_to, etc in
>>> the task itself then calling deploy.update. I'm wondering if this is a
>>> reasonable approach, or these should definitely be in different Cap
>>> files for some reason?
>>
>>> Thanks.
>>
>>> --
>>> * You received this message because you are subscribed to the Google Groups
>>> "Capistrano" group.
>>> * To post to this group, send email to [email protected]
>>> * To unsubscribe from this group, send email to
>>> [email protected] For more options, visit this group
>>> athttp://groups.google.com/group/capistrano?hl=en
>
> --
> * You received this message because you are subscribed to the Google Groups
> "Capistrano" group.
> * To post to this group, send email to [email protected]
> * To unsubscribe from this group, send email to
> [email protected] For more options, visit this group at
> http://groups.google.com/group/capistrano?hl=en
--
* You received this message because you are subscribed to the Google Groups
"Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to
[email protected] For more options, visit this group at
http://groups.google.com/group/capistrano?hl=en
