frederikheld

My webhoster all-inkl.com is great, but they have a very verbose auto-logout policy in their "Kundenadministrationssystem (KAS)" which drives me nuts because it kicks me out after only ~10 minutes of inactivity. And as the automatic logout is an irregular session termination, they will request 2FA upon login. ~10 minutes is by far not enough if I do configurations across multiple different systems, need time to do research in between and maybe even have a break. So a huge portion of my workday is wasted with the tedious login process and then looking for the place where I have left off.

I do not understand why this policy needs to be that strict (nobody uses public internet cafés anymore to configure their webhosting) and why they do not allow me to change this policy according to my needs.

Fortunately this can be worked around on my side with the help of this Violentmonkey script:

// ==UserScript==
// @name        New script all-inkl.com
// @namespace   Violentmon

frederikheld

If you create a new release in GitHub, you will either create a new tag (which will point to the most recent commit on main) or choose an existing tag (that might point to an older commit).

If you want to create releases from old commits (e.g. because you forgot to create a realease or didn't work with releases back then), there is a problem with this: when creating a tag for a specific commit in the past, GitHub only lets you pick from the most recent commits, so the commit you want to tag will not show up in the list.

Luckily, you can tag older commits locally [1]:

1. Find the commit on GitHub. If it is from a Pull Request, you can look into the closed Pull Requests. Within the PR you'll find a link to the commit.
2. Copy the commit hash from yo

frederikheld

#!/bin/sh

if [ "$(id -u)" -ne 0 ]
then
    echo "This scripts needs elevated privileges. Please run as sudo!"
    echo "Correct usage:"
    echo "  $ sudo sh $(basename "$0")"
    exit 1
fi