Config and Environment Variables #471
Description
Issues with configurations and environment variabls:
- env file stores both keys and also configurations
- for local development need to repeat same .env file variables in different packages
- for dockerized local development, docker-compose is outdated but is good because it only needs one .env file
Configurama Plan:
- remove non-keys from env file storage (should not be kept together)
- put non-key configurations in local json files that are read in one place and used for testing locally or in docker (makes local onboarding/testing easier)
- for prod, configurations will be read from configurama api and auto-updated in background (no more server restarts to update rpc's)