Suggesting using Secrets instead

[benguild]

#1

[Sh4yy]

Thanks for looking into this! I find setting up env variables much easier and straightforward, specifically when doing local development and deploying without using Wranger. I'd say a better solution would be supporting both but giving a higher priority to secrets so it is used if set. Otherwise, we default back to env variables.

Happy to implement it tomorrow morning!

[benguild]

It's just a README change. Deploying a secret with the same name works the same way but doesn't store it in the file, which risks it being accidentally committed to the repo.

[Sh4yy]

I apologize! You are right!

Two things before I merge,

1. We still need [env.production] in the toml file. I currently get this warning:

    - No environment found in configuration with name "production".
      Before using `--env=production` there should be an equivalent environment section in
  the configuration.
  
      Consider adding an environment configuration section to the wrangler.toml file:
      ```
      [env.production]
      ```

2. Also, I think this would be a better description for the third step:

Use the command npx wranler secret put --env production TOKEN to create a secure token. You are then prompted to enter a random secret value. This will be used to authenticate your requests. You can also set this value directly in your Cloudflare dashboard.

[benguild]

I'll tweak it right now, hang on

[benguild]

pushed 26aa4bc

[Sh4yy]

Merged! Thank you.