Adjust the way private scripts are run
- the exact scripts that are run by `run-private-scripts` is not disclosed here - the private scripts were adjusted so that they can be run as often as desired and always result in the same idempotent result - consequently, the private scripts are now always triggered by `update-machine` as well
This commit is contained in:
parent
f3f2417442
commit
ac4bad32f5
1 changed files with 3 additions and 0 deletions
|
@ -140,6 +140,8 @@ _restore_gnome() {
|
||||||
|
|
||||||
|
|
||||||
run-private-scripts() { # in the Nextcloud
|
run-private-scripts() { # in the Nextcloud
|
||||||
|
sudo --validate || return
|
||||||
|
|
||||||
if [ -d "$HOME/data/getraenkemarkt/shell" ]; then
|
if [ -d "$HOME/data/getraenkemarkt/shell" ]; then
|
||||||
for file in $HOME/data/getraenkemarkt/shell/*.sh; do
|
for file in $HOME/data/getraenkemarkt/shell/*.sh; do
|
||||||
source $file
|
source $file
|
||||||
|
@ -160,6 +162,7 @@ update-machine() {
|
||||||
_update_zsh
|
_update_zsh
|
||||||
_update_python
|
_update_python
|
||||||
_restore_gnome
|
_restore_gnome
|
||||||
|
run-private-scripts
|
||||||
|
|
||||||
sudo --reset-timestamp
|
sudo --reset-timestamp
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue