On Thu, May 29, 2014 at 1:23 PM, Mark Chu-Carroll
wrote:
> The reason that I use an alias for rbt isn't because I'm trying to save
> keystrokes. It's because "-o", "-g" and "-r" mean nothing to me. More
> keystrokes is fine, if it comes with clarity - that's why I went along with
> dropping the
On Thu, May 29, 2014 at 1:23 PM, Mark Chu-Carroll
wrote:
> The reason that I use an alias for rbt isn't because I'm trying to save
> keystrokes. It's because "-o", "-g" and "-r" mean nothing to me. More
> keystrokes is fine, if it comes with clarity - that's why I went along with
> dropping the
The reason that I use an alias for rbt isn't because I'm trying to save
keystrokes. It's because "-o", "-g" and "-r" mean nothing to me. More
keystrokes is fine, if it comes with clarity - that's why I went along with
dropping the automatic shorthands.
The stuff that you can do with Brian's alias
I see the point about having global client defaults, but I still think we
should avoid inferring the jobkey from the home directory. I'd suggest only
inferring command_defaults, or even storing them separately - but this also
adds complexity. Interested in what other people think here.
With regard
WRT to the home directory fallback: I'm not hugely committed to it, but
I've discussed this with a couple of people, and all have liked it, for one
big reason: they're using git in the twitter codebase - so the working
directory that they use contains a ton of different projects. They can't
just pu
I am a huge +1 on the idea of storing my run configurations in config files
so that I don't need to type them out every time. I also really like the
idea of command defaults.
I do however have a couple of comments about the details of the proposal.
I'm a little concerned about the fallback to the
I think that the answer there is that we want to *reduce* scripting, not
*eliminate* it.
Scripting happens for a bunch of different reasons:
(1) Filling functional gaps, where the original application is missing some
key functionality that users really need. For example, in my last job, we
had a s
>
> In order to avoid these problems, users set up custom scripts
> that make it easy for them to run commands like "`myservice start`",
> instead of "`aurora job create west/markcc/prod/myserver
> src/main/aurora/myservice/myservice.aurora`"
> To reduce this...
The missing detail seems to be why
