Re: [Fab-user] default "global" domain but not host?

[Jeff Forcier]

Hi Jorge,

I personally have no need for it since my workstation (all my internal
systems, actually) make use of the DNS 'domain' and 'search' options,
so that if I refer to a non-FQDN hostname, the domain is automatically
appended for me. This is the best idea if your 'example.com' is
relatively static.

Otherwise (such as if you or another user is a freelancer/consultant
and works at multiple domains) your approach would be the best way to
implement this as things currently stand.

Long-term, it would also make sense to factor into the (vague) plans I
currently have about making host info more robust. E.g. a 'hostgroup'
object, which could then have a 'domain' attribute automatically
appended to its hosts' domain names at runtime; or simply host objects
that can have "aliases" as well as FQDNs, where we can refer
internally to the shorter names but Fabric uses the FQDNs to actually
connect.

Best,
Jeff

On Tue, Jul 7, 2009 at 5:21 PM, Jorge Vargas<address@hidden> wrote:
> Hi guys,
>
> I have been thinking of this and I'll like your opinion.
>
> most (if not all) of the time you will be handling several
> environments for the same project which normally contain the same
> domain. The classical example will be
>
> test.example.com
> prod1.example.com
> prod2.example.com
> db1.example.com
> db2.example.com
>
> so I was thinking of having something along the lines of
>
> env.domain = 'example.com'
>
> @hosts('staging')
> def install_htaccess():
> .....
>
> @hosts('prod1','prod2')
> def install_ssl():
> .....
>
>
> is this something worth considering adding to fabric itself? for api
> clarity I think we should pick a different function make @machine or
> @subhost (I'm terrible with names)
>
>
> _______________________________________________
> Fab-user mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fab-user
>