You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: