Worker environnments as multi-tenant solution: are workers env broken ?
I'm trying to achieve one
default env: clientA.com
env
only 2 vars differs from client A to B that's why I don't want to create 2
Thing is: for
For woker I haven't found this.
The github integration keeps running
Deploy command:
Version command:
here is my wrangler.json: https://gist.github.com/tristanbes/51ad39218d21329f27be179a73bb7281
Thanks for your help
wrangler.json to get: default env: clientA.com
env
welcome: clientB.com only 2 vars differs from client A to B that's why I don't want to create 2
wrangler.json file and leverage https://developers.cloudflare.com/workers/wrangler/environments/Thing is: for
pages you have a select on the cloudflare dashboard that shows the different environements (and their vars/configuration/secrets)For woker I haven't found this.
The github integration keeps running
npx opennextjs-cloudflare deploy --env=welcome && npx opennextjs-cloudflare deploy but :- default env (
clientA.com) works fine - nothing is accessible on
clientB.com - no errors on the build or deploy (both env) command.
- no reference to the
welcomeenv for ClientB, wether on cloudflare workers list, nor inside the worker project (johndoe)
npx opennextjs-cloudflare buildDeploy command:
npx opennextjs-cloudflare deploy --env=welcome && npx opennextjs-cloudflare deployVersion command:
npx wrangler versions uploadhere is my wrangler.json: https://gist.github.com/tristanbes/51ad39218d21329f27be179a73bb7281
Thanks for your help
