Jesper Pedersen

Please, no new pull requests. Force push instead. https://git-scm.com/book/en/v2

One pull request per change - you can squash and force push in order to update the pull request.

Please, reopen if you think it is necessary and it is up-to-date

I think it would be better to put information like this in a `doc/DEVELOPMENT.md` file since we can assume that people using the `master` branch are developers. Maybe we can...

Remember to add yourself to the `AUTHORS` file as well

Ideally, `master` is stable with the up-coming features. However, it may be unstable during certain times in order to help development in a certain area. `config-get` and `config-set` are the...

Please, reopen and update if you think it is still needed

Let it go to a separate process. We just need to update the frontend passwords and then serve them to the vault binary

No, let `pgagroal` update the front-end passwords. And then, the `vault` process ask for the current password whenever there is a client request for it

In pgagroal there should be a `GET_PASSWORD` management command. pgagroal should not "talk" to pgagroal-vault in any way. pgagroal should handle the changing of the frontend end user passwords. pgagroal-vault...