diff options
author | Nick Hilliard <nick@foobar.org> | 2016-07-09 22:14:39 +0100 |
---|---|---|
committer | Nick Hilliard <nick@foobar.org> | 2016-07-09 22:14:39 +0100 |
commit | 7e41c5bf22ca82e636d511a54a7cf2e9bc8c9362 (patch) | |
tree | 157448e95296ea3781b4fdf4eff8169a99e6364e /README.md | |
parent | a058d6ab423944e106c4c2941e026e4519fed2fa (diff) |
oxidized should be run as its own username, not as root
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -166,6 +166,14 @@ gem install oxidized-script oxidized-web Oxidized configuration is in YAML format. Configuration files are subsequently sourced from ```/etc/oxidized/config``` then ```~/.config/oxidized/config```. The hashes will be merged, this might be useful for storing source information in a system wide file and user specific configuration in the home directory (to only include a staff specific username and password). Eg. if many users are using ```oxs```, see [Oxidized::Script](https://github.com/ytti/oxidized-script). +It is recommended practice to run Oxidized using its own username. This username can be added using standard command-line tools: + +``` +useradd oxidized +``` + +It is recommended not to run Oxidized as root. + To initialize a default configuration in your home directory ```~/.config/oxidized/config```, simply run ```oxidized``` once. If you don't further configure anything from the output and source sections, it'll extend the examples on a subsequent ```oxidized``` execution. This is useful to see what options for a specific source or output backend are available. You can set the env variable `OXIDIZED_HOME` to change its home directory. |