Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Correct auto-updater to netdata-updater #5281

Merged
merged 4 commits into from
Jan 28, 2019
Merged

Correct auto-updater to netdata-updater #5281

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
33960ca
Correct auto-updater to netdata-updater
cakrit Jan 28, 2019
1a29f6a
Update UPDATE.md
cakrit Jan 28, 2019
6d7fc7a
Update UPDATE.md
cakrit Jan 28, 2019
a469f07
Update UPDATE.md
cakrit Jan 28, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions packaging/installer/UPDATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
cakrit marked this conversation as resolved.
Show resolved Hide resolved

```sh
# go to the git downloaded directory
Expand Down Expand Up @@ -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
cakrit marked this conversation as resolved.
Show resolved Hide resolved
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.
cakrit marked this conversation as resolved.
Show resolved Hide resolved

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.
Expand Down