openboxes / openboxes/openboxes-mobile
Configure .env for environment variables
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 13
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 7
Description
Details
https://docs.expo.io/guides/environment-variables/
Expected Behaviors
- Should be used for any environment (development, staging, production) to store environment variables that will be used for API URLs, keys, secrets, etc.
- Should not store .env file in repository (need to figure out way to copy variables to compiled application without leaking secrets)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Expo environment-variables guide, then inspect the repository's current application and build configuration; the issue does not name a file or test. Done means development, staging, and production variables support API URLs and keys while secrets are not committed or leaked in the compiled application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- mobile-dev, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100