After some testing and manually trying to set sane file modes, it turns out the umask still applies. So it seems the logical way to handle this is to actually rely on the OS umask to set proper permissions.
- refactor clientManager.js to allow configuration parsing as a serparate
function.
- refactor clientManager.js to add configuration writing function.
- add server.js changes to allow for new password-change functionality
- add password change ui to "settings" screen
- refactor client.js to use new clientManager functionality for saving
the configuration files
Autoload now uses kernel events to watch files on disk. This greatly increases performance and reliability. Autoload will also watch user.json files for changes and reload the users data.
Listens for a 'SIGHUP' signal and reloads users when it gets one. The signal won't be listened to if its running on Windows as a SIGHUP indicates a console window closing.
