Re:Show HN: Config.ly – Never hardcode your data again
by jeremyis on Wednesday November 11, 2020 @01:14PM
(#25061007)
Thanks for the feedback. The goal right now is not to store sensitive data in Config.ly - your read API keys will be on your clients - and so in theory anyone who can read that source code can fetch your keys.
> Who has access to each client's database? Is it audited? Is it encrypted at rest? I'm sure it is, but Config.ly would be wise to add this information to avoid fears.
This is great feedback, thank you.
Re:Show HN: Config.ly – Never hardcode your data again
by munro on Wednesday November 11, 2020 @01:03PM
(#25060908)
Ohhh, that's such a great idea. I've done that before for TravisCI, now that I remember, it's really slick.
https://docs.travis-ci.com/user/environment-variables/#defin...
Who has access to each client's database? Is it audited? Is it encrypted at rest? I'm sure it is, but Config.ly would be wise to add this information to avoid fears.
Also you can store encrypted secrets in Git just fine, there are a number of methods to do so very safely.