How to set environment variables without pushing them to remote

Original message was deleted

Walshy•1/1/25, 11:35 PM

The way to do it is wrangler.toml

People can set the vars themselves when cloning. Common practice already for things like secrets

Walshy•1/1/25, 11:35 PM

Either way people would need to set them, I'm not sure why you wouldn't use wrangler.toml

Original message was deleted

Walshy•1/1/25, 11:36 PM

Why? You should use secrets for sensitive things

Walshy•1/1/25, 11:36 PM

Ok?

Walshy•1/1/25, 11:36 PM

Why not?

Walshy•1/1/25, 11:36 PM

Having production, staging, whatever variables committed is normal

Walshy•1/1/25, 11:38 PM

Very normal to commit that and people set their own.

You can be janky and not commit it and fill it in at deploy time but that's not a great situation

James•1/1/25, 11:39 PM

Document it in the readme then and in code, check for it not existing and throw an error?

Walshy•1/1/25, 11:40 PM

Then do an alternative approach like filling in the file at deploy time

Walshy•1/1/25, 11:40 PM

I wouldn't recommend it but if you don't want to commit, that's your option

Walshy•1/1/25, 11:40 PM

Locally you have .dev.vars

Original message was deleted

James•1/1/25, 11:40 PM

Or set it to PLACEHOLDERPLACEHOLDER or XXXXXX?

Walshy•1/1/25, 11:40 PM

Having a GitHub action in the repo is also standard practice

Walshy•1/1/25, 11:41 PM

Yes. .dev.vars local, wrangler toml had empty value or whatever and then fill in at deploy

Walshy•1/1/25, 11:42 PM

GitHub actions + actions env vars?

Original message was deleted

Walshy•1/1/25, 11:42 PM

Indeed. I said I don't recommend but that's an option here :LuL:

Original message was deleted

James•1/1/25, 11:43 PM

It doesn’t - you can set vars via cli too

Walshy•1/1/25, 11:43 PM

Could also use json, much easier to set on the fly than toml

Original message was deleted

James•1/1/25, 11:44 PM

It doesn’t write to toml, no

Walshy•1/1/25, 11:45 PM

No, it just adds it to the worker at upload time just like how it reads the toml and sets those at upload time

Walshy•1/1/25, 11:45 PM

--var "ABC=$MY_VARIABLE"

Can't remember if it's --var or --vars but something like that

Original message was deleted

James•1/1/25, 11:46 PM

I think you’re misunderstanding how Workers get deployed and run. .dev.vars is literally for this - env and secrets.
You read both on

env

env

in your handlers. Then when you deploy, you set these at deploy time in something like GitHub actions.

James•1/1/25, 11:47 PM

No it doesn’t

Walshy•1/1/25, 11:47 PM

Oh right it's colon not equals
https://developers.cloudflare.com/workers/wrangler/commands/#deploy

wrangler deploy --var "CF_TURNSTILE_SITE_KEY:$CF_TURNSTILE_KEY"wrangler deploy --var "CF_TURNSTILE_SITE_KEY:$CF_TURNSTILE_KEY"

Original message was deleted

James•1/1/25, 11:48 PM

Don’t put env vars in wrangler.toml and then it solves your problem?

James•1/1/25, 11:48 PM

No, you would set that in your deploy script like via GitHub actions + wrangler-action

Walshy•1/1/25, 11:50 PM

Can also --keep-vars and avoid Wrangler removing them but again, do not recommend

James•1/1/25, 11:50 PM

That’s fine. You can GitHub actions or some other CI, set env there and then add these in your action config

James•1/1/25, 11:50 PM

Take a look at https://github.com/cloudflare/wrangler-action

GitHub

GitHub - cloudflare/wrangler-action: 🧙‍♀️ easily deploy cloudflare ...

easily deploy cloudflare workers applications using wrangler and github actions - cloudflare/wrangler-action

James•1/1/25, 11:51 PM

Yes, if a user wants to deploy your app, editing a config and running some commands is common

Walshy•1/1/25, 11:51 PM

Clone, add GitHub actions env vars, done

James•1/1/25, 11:53 PM

Okay, well there’s a lot of solutions here we’ve given for your issue. If you think there’s improvements Cloudflare could make to its docs or wrangler itself for environment handling, I’d encourage you to open issues in those repos.

Walshy•1/1/25, 11:57 PM

You can specify a config file to read with --config so sure

GardenSnakes•1/3/25, 9:19 AM

Locally use your .dev.env file and when deploying use a GitHub action which supplies the secrets. Should be a way to do so in the arguments of the GitHub actions

Original message was deleted

GardenSnakes•1/3/25, 12:20 PM

What do you mean only work for secrets?

GardenSnakes•1/3/25, 12:20 PM

You can put in your environment specific variables there?

GardenSnakes•1/3/25, 12:20 PM

That's why you use the pipeline

GardenSnakes•1/3/25, 12:20 PM

And deploy it with the variables

GardenSnakes•1/3/25, 12:21 PM

Which get injected from the pipeline

Original message was deleted

GardenSnakes•1/3/25, 12:21 PM

So you didn't do what I said. Show me your pipeline

GardenSnakes•1/3/25, 12:21 PM

How does it look

GardenSnakes•1/3/25, 12:22 PM

What do you mean with those are now in the dev.env? Dev.env is for local development

GardenSnakes•1/3/25, 12:22 PM

You don't push that to your repo

GardenSnakes•1/3/25, 12:22 PM

How do you want your production deployment process to look like then?

GardenSnakes•1/3/25, 12:23 PM

And what is the current issue you want to solve?

Original message was deleted

GardenSnakes•1/3/25, 12:24 PM

Yes that's also the case here right?

GardenSnakes•1/3/25, 12:24 PM

You dev.env isn't tracked

GardenSnakes•1/3/25, 12:25 PM

So what you are trying to say is, site key is a text variable that is different for all environments and has to be tracked?

GardenSnakes•1/3/25, 12:25 PM

And used for deployment

How to set environment variables without pushing them to remote

Similar Threads

Similar Threads

Similar Threads