Specifying local_path or local_dir makes no sense for upload_project since put supports glob patterns (in fact all of upload_project is somewhat questionable).
However, rsync_project is a little bit different - put is not a real substitude here because we expect rsync to handle certain cases much more efficiently (like a project with some large but seldomly changing files). So I think this is a feature that makes sense to implement. On Thu, Apr 16, 2009 at 8:49 AM, Paul Baumgart <[email protected]> wrote: > The local path is the directory from which you run Fabric. Currently, > the only way to approximate specifying the local path is by explicitly > excluding everything except the files you want to upload. > > I support adding a local_path parameter, but I suppose it would > slightly change the original intent of the function (as an alternative > to upload_project). The reason I didn't add this from the get-go was > because of my sense that Christian tends towards the minimalist, but > with his blessing I'd be happy to add this functionality. > > Paul > > On Mon, Apr 13, 2009 at 12:43 PM, Domen Kožar <[email protected]> wrote: >> rsync_project currently only supports to specify remote_dir, how is the >> local project path determined? if it can't be changed, that would be a >> nice feature because sometimes glob is just not enough. >> >> d. >> >> >> _______________________________________________ >> Fab-user mailing list >> [email protected] >> http://lists.nongnu.org/mailman/listinfo/fab-user >> > > > _______________________________________________ > Fab-user mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/fab-user > -- Venlig hilsen / Kind regards, Christian Vest Hansen. _______________________________________________ Fab-user mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/fab-user
