Allow specifying .toml file in wrangler build

[ghost]

Currently, wrangler build uses the wrangler.toml file, but there are situations where it would be ideal to have multiple deploys of the same code, either for staging environments or for situations where you want to deploy to multiple zones or routes.

This would work well with the addition of the kv namespace bindings (#299), so that you could have a test namespace, with a test script, by specifying a "wrangler-test.toml" file.

I suggest wrangler build -c <file>.

This of course can be solved via a build script as well, but I'd prefer to have something baked in.

[EverlastingBugstopper]

This seems like an alternative solution to what is proposed here: #220

cc: @xtuc

[ghost]

Yes, that could work.

There may be advantages to allow specifying a file instead of an env, so that you can deploy one script to multiple different zones?

Edit: I see it was proposed to allow arbitrary environments, that could work. We can close this.

[EverlastingBugstopper]

Thanks! Closing in favor of #220