fix the fail2ban issues and other things

updates.d/17-email-watch.sh

@@ -0,0 +1,7 @@
+#!/bin/bash
+
+COREDESKTOP="$HOME/.local/share/coredesktop"
+
+run_update() {
+  bash "$COREDESKTOP/system/email-watch.sh"
+}

updates.d/40-mise.sh

@@ -1,16 +1,25 @@
 #!/bin/bash
 
-# Answer yes to any mise prompt (e.g. trusting config files)
-export MISE_YES=1
+# Upgrade the languages you installed with mise (configure languages), within
+# the versions you chose: ruby@latest moves to the newest Ruby, java@21 stays 21.
+# mise itself comes from pacman, which updates it.
 
-echo "Updating mise..."
-mise self-update -y
+is_installed() {
+  command -v mise > /dev/null && [ -n "$(mise ls --global --quiet 2> /dev/null)" ]
+}
 
-echo "Updating Ruby and Rails..."
-mise upgrade --bump ruby
-mise reshim
-# A new Ruby's bundled gems (e.g. minitest) come with executables RubyGems
-# doesn't recognise as its own, so gem update stops to ask whether to overwrite
-# them. Regenerating them first lets the update go through without asking.
-gem pristine --all --only-executables > /dev/null
-gem update
+run_update() {
+  # Answer yes to any mise prompt (e.g. trusting config files)
+  export MISE_YES=1
+  # From home, so a project's mise.toml in the current directory doesn't count
+  cd "$HOME" || return 1
+
+  echo "Updating languages installed with mise..."
+  mise upgrade || return 1
+
+  # A new Ruby gets Rails from ~/.default-gems; this updates it between Rubies
+  if mise exec -- gem list -i rails &> /dev/null; then
+    echo "Updating Rails..."
+    mise exec -- gem update rails bundler || return 1
+  fi
+}