By default, everything functions the same. But if the `DISABLE_CONFIG_BACKUPS` env var is set, then when the user saves the config to disk (via UI, calling the save-config endpoint), then the previous config will not get coppied/backedup to the BACKUP_DIR (user-data/config-backups) anymore. Also added docs for this change. This option might be useful on file systems with restricted permissions (if /app/user-data/config-backups doesn't have create/write access), or when the user just doesn't want a ton of backup files for every single litttle config change.
Adds a timeout to prevent ever lasting requests, surrounds JSON parse with try catch when header missing uses a 400 status code instead of 500 and fixes the error messaging for this
transition class names (-enter → -enter-from), ::v-deep → :deep(), $router.currentRoute → $route, removed duplicate proxyReqEndpoint overrides that shadow the mixin
Plus some error handling and robustness improvments to global error handler, try-catch on all JSON.parse/yaml.load from localStorage/config, null-checks on DOM lookups, .catch() on unhandled axios promises, sanitized v-html in Footer
And removes stake weback and vue cli cleanup of crap.
I ran into a issue running dashy in a podman oci container with the default value for public & private key paths not being set the same way in healthcheck.js vs ssl-server.js
This difference was allowing SSL to start causing the healthcheck to get a 302 redirect to https .
This change adds in the same default path vars and i am going to say similar behavior that ssl-server.js uses. i tried to match the same style as the existing code between the two files
another alternative is to set `SSL_PUB_KEY_PATH` and `SSL_PRIV_KEY_PATH` in the compose file as env vars
but after seeing #843 which lead me #768 and then finding
#1410
ill be honest this probably solves #843 and #1410 i dont think this totally solved #768 tbh. i had a hard time following that thread
