On Thu, Feb 3, 2011 at 4:37 AM, Daniel Pope wrote:
> Ew :-P
Yea, it's not as nice as your decorator approach, in terms of the top
level API; on the other hand, I think a simple, clean function might
be a more straightforward approach. The more decorators we use the
more magical stuff becomes.
A
On 02/02/11 23:48, Jeff Forcier wrote:
def deploy():
execute(update_django_project)
execute(update_db)
execute(update_services)
Ew :-P
Point being that in order to get the extra "magic" of honoring
host/role decorators, we'd need to ask users to move from calli
> What I'd love, and I suspect Carlton would as well, is the ability to wrap
> all those up in a single function
>
> def deploy():
> update_django_project()
> update_db()
> update_services()
>
> And thus be able to deploy with one line
>
> $ fab production deploy
This is a kn
I think what Carlton is looking for is a little different, though I do like
your method. I think I have the same needs as Carlton. Likewise, I'm running
a Django project with multiple servers acting in different roles. Fabric's
roles are great to handle that. So I currently have something l
Hi Carlton,
What I've done is perhaps not quite your use case as I separate my hosts on a
project basis, but maybe you can make it work for you. I have separated
choosing the host from my other tasks, with something like this:
@roles('A_servers')
def projA():
'''Specifies that subsequent c
