Publish .env

[wcjord]

We want to have a .env that we can share with the project to allow easy collaboration. Are we at the point where we can remove any sensitive info from it?

[ggurdin]

These .env variables are still being used:

CHOREO_API
FRONTEND_URL

SYNAPSE_URL
CHOREO_API_KEY

RC_PROJECT
RC_GOOGLE_KEY
RC_IOS_KEY
RC_STRIPE_KEY
RC_OFFERING_NAME

STRIPE_MANAGEMENT_LINK

The revenue cat keys are public keys with read access, used to set up the revenue cat flutter SDK / get user's subscription info. They do not have write access.

[wcjord]

Sounds like this should be fine? @kwek20 Mr. CISO - do you see any issue with these being shared broadly?

[kwek20]

Nope all good! all public keys

[wcjord]

Is there any issue with adding the env directly into the project in this case?