You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- The script make system updates with apt/dnf/pacman/apk or yum on all nodes/LXCs and VMs (if VMs prepared for that)
48
-
- Make a snapshot befor update (if your storage support it - [look here](https://pve.proxmox.com/wiki/Storage)). If not supported, you can choose to make a real backup, but this must be enabled in `update.conf` by user (take long time!)
49
-
- After all, the updater makes an little cleaning (like `apt autoremove`)
44
+
- The script makes system updates with apt/dnf/pacman/apk or yum on all nodes/LXCs and VMs (if VMs prepared for that)
45
+
- Make a snapshot before update (if your storage support it - [look here](https://pve.proxmox.com/wiki/Storage)). If not supported, you can choose to make a real backup, but this must be enabled in `update.conf` by user (take long time!)
46
+
- After all, the updater makes a little cleaning (like `apt autoremove`)
50
47
- If the script detects "extra" installations, it could update this also. Look in config file, for that.
**! For Cluster Installation, you only need to install on one Host !**
61
58
62
-
The nodes need to know each other. For that please edit the `/etc/hosts` file on each node. Otherwise you can use the GUI (NODE -> System -> Hosts)
59
+
The nodes need to know each other. For that please edit the `/etc/hosts` file on each node. Otherwise, you can use the GUI. (NODE -> System -> Hosts)
63
60
64
61
Example add:
65
62
```
@@ -76,7 +73,6 @@ After that make the fingerprints.
76
73
The used sequence can be check, if you run `awk '/ring0_addr/{print $2}' "/etc/corosync/corosync.conf"` from the host, on which Proxmox-Updater is installed.
77
74
So connect from first node (on which you install the Proxmox-Updater) to node2 with `ssh pve2`. Then from node2 `ssh pve3`, and so on.
78
75
79
-
80
76
## If you want to update the VMs also, you have two choices:
81
77
1. Use the "light and easy" QEMU option
82
78
@@ -86,7 +82,6 @@ So connect from first node (on which you install the Proxmox-Updater) to node2 w
86
82
87
83
more infos here: [SSH Connection](https://github.com/BassT23/Proxmox/blob/master/ssh.md)
If updater detects installation: (disable, if you want in `/root/Proxmox-Updater/update.conf`)
102
96
- PiHole
@@ -105,7 +99,6 @@ If updater detects installation: (disable, if you want in `/root/Proxmox-Updater
105
99
- Octoprint
106
100
- Docker Container Images
107
101
108
-
109
102
# Config File:
110
103
The config file is stored under `/root/Proxmox-Updater/update.conf`
111
104
@@ -117,30 +110,34 @@ With this file, you can manage the updater. For example; if you don't want to up
117
110
- "stopped" or "running" LXC/VM
118
111
- "only" or "exclude" LXC/VM by ID
119
112
120
-
121
113
# Welcome Screen:
122
-
The Welcome Screen is an extra for you. Its optional!
114
+
The Welcome Screen is an extra for you. It's optional!
123
115
124
116
- The Welcome-Screen brings an update-checker with it. It check on 07am and 07pm for updates via crontab. The result will show up in Welcome-Screen (Only if updates are available).
125
-
- The update-checker also use the config file!
117
+
- The update-checker also uses the config file!
126
118
- To force the check, you can run `/root/Proxmox-Updater/check-updates.sh` in Terminal.
127
119
- You can choose, if neofetch will be show also (if neofetch is not installed, script will make it automatically)
128
120
129
-
130
121
# Beta Testing:
131
-
If anybody want to help with failure search, please test our beta (if available).
122
+
If anybody wants to help with failure search, please test our beta (if available).
0 commit comments