See my other guides for SSL certificates on Pi-hole v6:
Pi-hole v6 introduces changes to its web server:
- Embedded Web Server – Pi-hole no longer relies on
lighttpd
.
See my other guides for SSL certificates on Pi-hole v6:
Pi-hole v6 introduces changes to its web server:
lighttpd
.See my other guides for SSL certificates on Pi-hole v6:
Pi-hole v6 introduces changes to its web server:
lighttpd
.# Applied to namespace "unifi" with kustomize | |
apiVersion: v1 | |
kind: ServiceAccount | |
metadata: | |
name: secret-creator | |
--- | |
apiVersion: rbac.authorization.k8s.io/v1 | |
kind: RoleBinding | |
metadata: | |
name: secret-creator-role-binding |
# Applied to namespace "unifi" with kustomize | |
apiVersion: v1 | |
kind: ServiceAccount | |
metadata: | |
name: secret-creator | |
--- | |
apiVersion: rbac.authorization.k8s.io/v1 | |
kind: RoleBinding | |
metadata: | |
name: secret-creator-role-binding |
#!/bin/bash | |
# Simple script to change admin login timeout in pihole version 5.17 and up. | |
# Note that some versions of pihole used 'loginpage.php' instead of 'login.php' | |
# make the script executeable by typing: | |
# chmod +x pihole-timeout.sh | |
# run it by typing: | |
# sudo ./pihole-timeout.sh | |
# Check if user is using sudo or is root: | |
if [[ $(/usr/bin/id -u) -ne 0 ]]; then |
1/03/2023
$ # Use Live CD to boot | |
$ sudo su # Switch to root | |
$ fdisk -l # Get names of root, boot & EFI partition names. you can also use blkid | |
$ # http://dadadom.de/2020/04/11/fix-fedora-uefi-boot-with-encrypted-partitions/ | |
$ udiskctl unlock -b /dev/nvme0n1p6 # unlock root luks partition | |
$ mount /dev/mapper/fedora_fedora-root /mnt # mount root partition | |
$ mount /dev/mapper/fedora_fedora-var /mnt/var | |
$ mount /dev/nvme0n1p5 /mnt/boot # mount boot partition |
In Fall 2023, Slack introduced an updated client with some unpopular UI changes. The tweaks in this document can be used to revert to the old client or hide the new side bar. These will reset every time you fully close Slack but they are easy to re-apply once you get the hang of it.
To run any of these scripts, you'll need to open the Dev Tools (or Console). You can do this by typing /slackdevtools
in a Slack channel or direct message. These are the same Dev Tools you'd get in Chrome if you hit F12. Along the top are tabs for Elements, Console, Sources, Network, etc. You'll want to paste these scripts into the Console tab at the >
prompt.
If Slack disables this command, then you can open Dev Tools by setting a system-wide environment variable and using a keyboard shortcut to open the console. If /slackdevtools
worked for you then you can skip these next two sections.
# krun busybox whoami | |
krun(){ | |
local NAMESPACE=default | |
local PRIVILEGED=false | |
while getopts 'n:pu:' OPT; do | |
case $OPT in | |
n) NAMESPACE=$OPTARG | |
;; | |
p) PRIVILEGED=true |