From 33960ca8ce470268412ea56b9dcd96536f3b4805 Mon Sep 17 00:00:00 2001 From: Chris Akritidis <43294513+cakrit@users.noreply.github.com> Date: Mon, 28 Jan 2019 14:27:37 +0100 Subject: [PATCH 1/4] Correct auto-updater to netdata-updater Also add info that .environment file gets updated by the netdata-installer.sh --- packaging/installer/UPDATE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packaging/installer/UPDATE.md b/packaging/installer/UPDATE.md index 56e1410278461f..e8546b906df355 100644 --- a/packaging/installer/UPDATE.md +++ b/packaging/installer/UPDATE.md @@ -11,7 +11,7 @@ The update procedure depends on how you installed it: ### Manual update to get the latest git commit -netdata versions older than `v1.12.0-rc2-52` had a `netdata-updater.sh` script in the root directory of the source code, which has now been deprecated. The manual process that works for all versions to get the latest commit in git is to use the `netdata-installer.sh`. The installer preserves your configuration. You just need to be mindful of any installer options you may have used to customize your original installation. +netdata versions older than `v1.12.0-rc2-52` had a `netdata-updater.sh` script in the root directory of the source code, which has now been deprecated. The manual process that works for all versions to get the latest commit in git is to use the `netdata-installer.sh`. The installer preserves your custom configuration and updates the the information of the installation in the `.environment` file under the user configuration directory. You just need to be mindful of any installer options you may have used to customize your original installation. ```sh # go to the git downloaded directory @@ -39,7 +39,7 @@ bash <(curl -Ss https://my-netdata.io/kickstart.sh --no-updates) _Please, consider the risks of running an auto-update. Something can always go wrong. Keep an eye on your installation, and run a manual update if something ever fails._ -Calling the `netdata-installer.sh` with the `--auto-update` or `-u` option will create an `auto-updater` script under +Calling the `netdata-installer.sh` with the `--auto-update` or `-u` option will create the`netdata-updater` script under either `/etc/cron.daily/`, or `/etc/periodic/daily/`. Whenever the `auto-updater` is executed, it checks if a newer nightly build is available and then handles the download, installation and netdata restart. Note that after Jan 2019, the `kickstart.sh` one-liner `bash <(curl -Ss https://my-netdata.io/kickstart.sh)` calls the `netdata-installer.sh` with the auto-update option. So if you just run the one-liner without options once, your netdata will be kept auto-updated. From 1a29f6a2a218e401124fc0fed09b0ced2b746e89 Mon Sep 17 00:00:00 2001 From: Chris Akritidis <43294513+cakrit@users.noreply.github.com> Date: Mon, 28 Jan 2019 19:20:22 +0100 Subject: [PATCH 2/4] Update UPDATE.md --- packaging/installer/UPDATE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packaging/installer/UPDATE.md b/packaging/installer/UPDATE.md index e8546b906df355..63bc80ee01ab16 100644 --- a/packaging/installer/UPDATE.md +++ b/packaging/installer/UPDATE.md @@ -40,7 +40,7 @@ bash <(curl -Ss https://my-netdata.io/kickstart.sh --no-updates) _Please, consider the risks of running an auto-update. Something can always go wrong. Keep an eye on your installation, and run a manual update if something ever fails._ Calling the `netdata-installer.sh` with the `--auto-update` or `-u` option will create the`netdata-updater` script under -either `/etc/cron.daily/`, or `/etc/periodic/daily/`. Whenever the `auto-updater` is executed, it checks if a newer nightly build is available and then handles the download, installation and netdata restart. +either `/etc/cron.daily/`, or `/etc/periodic/daily/`. Whenever the `netdata-updater` is executed, it checks if a newer nightly build is available and then handles the download, installation and netdata restart. Note that after Jan 2019, the `kickstart.sh` one-liner `bash <(curl -Ss https://my-netdata.io/kickstart.sh)` calls the `netdata-installer.sh` with the auto-update option. So if you just run the one-liner without options once, your netdata will be kept auto-updated. From 6d7fc7a5dc8a0d7657a4dd053933e0993fe5dd3c Mon Sep 17 00:00:00 2001 From: Chris Akritidis <43294513+cakrit@users.noreply.github.com> Date: Mon, 28 Jan 2019 19:22:18 +0100 Subject: [PATCH 3/4] Update UPDATE.md --- packaging/installer/UPDATE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packaging/installer/UPDATE.md b/packaging/installer/UPDATE.md index 63bc80ee01ab16..6c23958cdcd244 100644 --- a/packaging/installer/UPDATE.md +++ b/packaging/installer/UPDATE.md @@ -39,7 +39,7 @@ bash <(curl -Ss https://my-netdata.io/kickstart.sh --no-updates) _Please, consider the risks of running an auto-update. Something can always go wrong. Keep an eye on your installation, and run a manual update if something ever fails._ -Calling the `netdata-installer.sh` with the `--auto-update` or `-u` option will create the`netdata-updater` script under +Calling the `netdata-installer.sh` with the `--auto-update` or `-u` option will create the `netdata-updater` script under either `/etc/cron.daily/`, or `/etc/periodic/daily/`. Whenever the `netdata-updater` is executed, it checks if a newer nightly build is available and then handles the download, installation and netdata restart. Note that after Jan 2019, the `kickstart.sh` one-liner `bash <(curl -Ss https://my-netdata.io/kickstart.sh)` calls the `netdata-installer.sh` with the auto-update option. So if you just run the one-liner without options once, your netdata will be kept auto-updated. From a469f0733fa0e7daebb47937c38f9914c10fe60b Mon Sep 17 00:00:00 2001 From: Chris Akritidis <43294513+cakrit@users.noreply.github.com> Date: Mon, 28 Jan 2019 20:38:08 +0100 Subject: [PATCH 4/4] Update UPDATE.md --- packaging/installer/UPDATE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packaging/installer/UPDATE.md b/packaging/installer/UPDATE.md index 6c23958cdcd244..7c0be8323cf468 100644 --- a/packaging/installer/UPDATE.md +++ b/packaging/installer/UPDATE.md @@ -11,7 +11,7 @@ The update procedure depends on how you installed it: ### Manual update to get the latest git commit -netdata versions older than `v1.12.0-rc2-52` had a `netdata-updater.sh` script in the root directory of the source code, which has now been deprecated. The manual process that works for all versions to get the latest commit in git is to use the `netdata-installer.sh`. The installer preserves your custom configuration and updates the the information of the installation in the `.environment` file under the user configuration directory. You just need to be mindful of any installer options you may have used to customize your original installation. +netdata versions older than `v1.12.0-rc2-52` had a `netdata-updater.sh` script in the root directory of the source code, which has now been deprecated. The manual process that works for all versions to get the latest commit in git is to use the `netdata-installer.sh`. The installer preserves your custom configuration and updates the the information of the installation in the `.environment` file under the user configuration directory. ```sh # go to the git downloaded directory