You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could config values be encrypted by default and thus only edited through Nerthus?
I started thinking about how the only reason Nerthus now has such an amount of information is to help users easily spin up new Nerthus installs / environments. But what if Nerthus could help you write your git repo and maintain it. And all you had to do was add keys either directly in Nerthus or in the files and then Nerthus wrote encrypted values into the config fields. Then even if the git repo got leaked, it wouldn't be an issue.
This needs some more work and thought, but adding it for now.
The text was updated successfully, but these errors were encountered:
Could config values be encrypted by default and thus only edited through Nerthus?
I started thinking about how the only reason Nerthus now has such an amount of information is to help users easily spin up new Nerthus installs / environments. But what if Nerthus could help you write your git repo and maintain it. And all you had to do was add keys either directly in Nerthus or in the files and then Nerthus wrote encrypted values into the config fields. Then even if the git repo got leaked, it wouldn't be an issue.
This needs some more work and thought, but adding it for now.
The text was updated successfully, but these errors were encountered: