JSON configuration options

[HermannBjorgvin]

A config.json file is now in the root directory of the repository

Reading it from Javascript isn't an issue and scripts can be easily reconfigured to use values from that in the code. Bash scripts however will need some utility like JQ to read from the json file.

I timed the scripts in the repo last night and bash came ahead consistantly around 5-10 times faster than nodejs scripts. I think we should aim to keep the runtime down as much as possible to avoid too much bloat. We could also cache nodejs scripts at a specific interval for scripts that aren't very quick to change anyway.

What do people think is the best way to do this? I feel like this project would be better if you could edit a config file for appearance, key values, and so on.

[Heholord]

Wow cool idea, i will probably implement the interactive config setup tomorrow. I agree it would be really nice to have bash scripts for everything but i am not that used to writing in bash

[HermannBjorgvin]

We'll just make the environment optional, if people commit bash scripts that's nice but otherwise nodejs is fine.

The interactive config for example would be better suited for nodejs since it works so natively with json.

I think meanwhile I'll look at JQ for bash scripts, we should then provide examples for people wanting to adapt bash scripts to this library.

[Heholord]

I added the interactive console interface for the config, but i guess the config is not used jet. also the startupscript could be a great help

[satmandu]

Also FYI rather than specifying disks for hddtemp, one can also just do the following which will find all of the /dev/sd drives.

sudo hddtemp /dev/sd?