Currently we just store all the environment variables, including supposedly sensitive info (such as private keys) in a tree-commited file. This goes against common production practices and poses a big security threat, especially when we move on to testnet.
We could still have e.g. a .env.example with dummy values for developer reference, but otherwise a more robust mechanism is needed. This could stem off in two directions: one is the actual implementation of secrets (could be either or some of providers such as Google Cloud or Github CI or even at the Docker level). The other is actually implementing key generation for admin or other users and allow provision of custom keys.
Currently we just store all the environment variables, including supposedly sensitive info (such as private keys) in a tree-commited file. This goes against common production practices and poses a big security threat, especially when we move on to testnet.
We could still have e.g. a .env.example with dummy values for developer reference, but otherwise a more robust mechanism is needed. This could stem off in two directions: one is the actual implementation of secrets (could be either or some of providers such as Google Cloud or Github CI or even at the Docker level). The other is actually implementing key generation for admin or other users and allow provision of custom keys.