On Wed, Jul 27, 2011 at 5:13 PM, Michael Foord
<email address hidden> wrote:
> Using environment variables requires no particular support from sst -
> you could use those already if you wanted - so the only reason to add
> command line handling is if it is a nicer "ui" for users. I think it is.
True! I'll update the new account tests to have a default (staging)
but allow overriding with an env var. If that solves my use-case (as
we shouldn't have too many of these I think, and they should be
standard across all tests in a test run right?). So far I've only
found GMAIL_PASSWORD and BASE_URL.
@dsowen: using simple env vars would even enable you to define
profiles very easily:
$ source staging_profile
On Wed, Jul 27, 2011 at 5:13 PM, Michael Foord
<email address hidden> wrote:
> Using environment variables requires no particular support from sst -
> you could use those already if you wanted - so the only reason to add
> command line handling is if it is a nicer "ui" for users. I think it is.
True! I'll update the new account tests to have a default (staging)
but allow overriding with an env var. If that solves my use-case (as
we shouldn't have too many of these I think, and they should be
standard across all tests in a test run right?). So far I've only
found GMAIL_PASSWORD and BASE_URL.
@dsowen: using simple env vars would even enable you to define
profiles very easily:
$ source staging_profile
or profile
$ ./set_staging_
or whatever?