* nginx_proxy: Update run.sh info messages
In particular, note that generating dhparams will take some time.
* nginx_proxy: Bump version to 1.1
* nginx_proxy: Make HSTS configurable and optional
Unconditional HSTS breaks unencrypted connections to non-standard HTTP
ports on the same hostname. These ports be e.g. mapped outside of
hassio/nginx, and this can not be always circumvented by proxying them
beind nginx, because not all services behave properly behind a reverse
proxy.
Additionally, the unconditional HSTS includeSubDomains setting
hardcodes assumptions about subdomains that hassio does not
necessarily deal with at all.
* fix style
* nginx_proxy: Allow customization with included config files from /share
Provides a way to add additional configuration to the default, for
example proxy_pass locations before the default root location, as well
as additional complete server configs.
* nginx_proxy: Run logo.png through zopflipng -m
* nginx_proxy: Bump version to 1.0, add CHANGELOG.md
* Update CHANGELOG.md
* disabled StrictHostKeyChecking during ssh key validation
* adds support to (ssh cloned) github repositories on key validation
* update Changelog and config.json
* Add user/password support to git pull.
This can be used for private repositories that don't support ssh.
Ex: https://cloud.google.com/source-repositories/docs/
* Remove unnecessary err redirection.
* Bump git_pull version to 3.1
* Update config.json
* Update CHANGELOG.md
* Update CHANGELOG.md
* address commands
* new implementation for git pull
* implemented review comments: use absolute paths
* fixed linting errors and warnings
* fixed spellcheck hints, and ignored one of them
* Update config.json
* Create CHANGELOG.md
* Update Dockerfile
* Create build.json
* add new cli
* Fix StrictHostKeyChecking-related failure
For ssh-through git connections, the git pull fails because the host key will not be automatically added to known_hosts.
This should fix that by allowing the key to be put into the known_hosts.
Note that if the remote server ssh key changes, the git operation will fail. That seems a reasonably safe security fallback.
* Update config.json
* Update config.json
* Update run.sh
* Single quotes.. ?
* Nope.. single quotes did not work
* Splitting on space and putting it back together
Spaced..
* Gosh
* Update run.sh
* Cropping msg
Since we wish to output the results from tdtool in either way (error or regular response) i cropped the catching of output.
* Keep it simple.
* ...
* hmm
* Update run.sh
* Update run.sh
* Update run.sh
* Fix bash variable input
This will cause error in validation.
i have tried with
if ! msg="$(tdtool --"$input")"; then
if ! msg="$(tdtool --"${input}")"; then
if ! msg="$(tdtool --${input})"; then
without success.
The only one i got working in real life is the one in this PR.
* Trying variable with curlies
Changed frm only output errors to output all output from tdtool.
Enables listing of devices and sensors with output to add-on log.
* Update config.json
* fix not used exec
* fix lint
* update output
