Append the following to your HTTP conf for the specific Virtualhost you want to disable HTTP/2 for:

Protocols http/1.1

If you’re using Docker compose for having a declarative way to run your containers you might have found out that updating it requires some manual work. In this example we automate it using the following structure:

• Folder: /opt/docker-compose
• Container folders: /opt/docker-compose/«container»

Below is an example of my structure:

[root] docker-compose# ls -ld /opt/docker-compose/*
-rw-r--r-- 1 root root    0 Sep 11  2023 /opt/docker-compose/README.md
drwxr-xr-x 2 root root 4096 Sep 13  2023 /opt/docker-compose/bazarr
drwxr-xr-x 2 root root 4096 Sep 11  2023 /opt/docker-compose/deluge
drwxr-xr-x 2 root root 4096 Sep 16 15:51 /opt/docker-compose/homeassistant
drwxr-xr-x 2 root root 4096 Jul 26 10:04 /opt/docker-compose/jellyfin
drwxr-xr-x 2 root root 4096 Sep 13  2023 /opt/docker-compose/jenkins
drwxr-xr-x 2 root root 4096 Oct  1 10:14 /opt/docker-compose/openvpn
drwxr-xr-x 4 root root 4096 Sep 13  2023 /opt/docker-compose/pihole
drwxr-xr-x 2 root root 4096 Sep 11  2023 /opt/docker-compose/radarr
drwxr-xr-x 2 root root 4096 Dec  4  2023 /opt/docker-compose/ring-mqtt
drwxr-xr-x 2 root root 4096 Sep 11  2023 /opt/docker-compose/sonarr
-rwxr-xr-x 1 root root  349 Sep 11  2023 /opt/docker-compose/update.sh
drwxr-xr-x 2 root root 4096 Sep 13  2023 /opt/docker-compose/vaultwarden
drwxr-xr-x 3 root root 4096 Oct  1 10:33 /opt/docker-compose/your_spotify

All these folders contain a docker-compose.yaml or compose.yaml file which the docker-compose command will look for when executing commands like docker-compose up -d.

The update script

Place the update script in /opt/docker-compose/update.sh:

#!/bin/bash

## Variables
SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )"
RED="\e[31m"
ENDCOLOR="\e[0m"
DIRS=$(find $SCRIPT_DIR/* -type d)


## Update
for DIR in $DIRS
do
        echo -e "${RED}Checking update for ${DIR}...${ENDCOLOR}\n"
        cd $DIR
        docker-compose pull
        docker-compose up -d --remove-orphans
        cd $SCRIPT_DIR
done

Make it executable by setting the X bit on the script:

chmod 750 /opt/docker-compose/update.sh

You can now run the script manually from any directory to check if it works correctly. Notice the SCRIPT_DIR variable which will automatically look in the folders where the script is located and thus check it’s subdirectories.

SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )"

Example script output

Below a screenshot of how the output will look (screenshot, not text because of the colours.)

Setting up a cronjob

Place a cronjob as following to execute script periodically. In this case I placed it in /etc/crontab hence why you see the user (root) argument after the time.

Below example will run it every day at 1 AM:

0 1 * * * root bash /opt/docker-compose/update.sh

A blind poule is a list of randomly generated soccer score outcomes. The script I made favours the lower numbers first (because this is more likely to happen) but it can generate scores where one team scores 6 or 7 goals.

Requirements

• weasyprint
• numpy
• jinja2

Weasyprint can be installed using your distro’s package manager. The remaining Python modules can be installed using pip:

pip install numpy jinja2

The script

import random
import numpy as np
import datetime
from jinja2 import Template

# Set
generated_scores = set()

# Generate random scores
def generate_score():
    global generated_scores
    while True:
        # Generate random scores favoring towards lower values
        team1_score = max(0, int(np.random.normal(2, 1.5)))
        team2_score = max(0, int(np.random.normal(2, 1.5)))
        score = f"{team1_score}-{team2_score}"
        if score not in generated_scores:
            generated_scores.add(score)
            return score

# Reset the set
def reset_generated_scores():
    global generated_scores
    generated_scores = set()

# Render the Jinja2 template
def render_template(template_path, num_scores):
    with open(template_path, 'r') as f:
        template_content = f.read()
    
    template = Template(template_content)

    rendered_content = template.render(
        generate_score=generate_score,
        num_scores=num_scores,
    )
    
    return rendered_content

# Generate and save the template
def generate_markdown_file(template_path, output_path, num_scores):
    reset_generated_scores()  # Reset!
    rendered_content = render_template(template_path, num_scores)
    with open(output_path, 'w') as f:
        f.write(rendered_content)

# Call it
generate_markdown_file("pool-template.html", "pool.html", 50)

Jinja2 template for scores (save as pool-template.html)

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Blinde voetbalpoule</title>
<style>
  @page {
    size: A4;
    margin: 0;
  }

  table {
    width: 100%;
    font-size: 9px; /* Smaller font size */
  }

  th, td {
    padding: 2.2px; /* Smaller padding */
  }

</style>
</head>
<body>
<h3 style="text-align: center;">Blinde voetbalpoule</h3>
<h5 style="text-align:center;">____________ tegen ____________ </h5>
<h6>Inleg: €1 per nummer, prijs bij goede uitslag: €25</h6>
<table>
  <thead>
    <tr>
      <th style="width: 5%;">Nr.</th>
      <th style="width: 70%;">Naam deelnemer:</th>
      <th style="width: 20%;"></th>
      <th style="text-align:center; width: 30%;">Score</th>
    </tr>
  </thead>
  <tbody>
    {% for x in range(1, num_scores + 1) %}
    <tr>
      <td style="border: 1px solid black;">{{ x }}</td>
      <td style="border: 1px solid black;"></td>
      <td style="width: 20%;"></td>
      <td style="text-align:center;border: 1px solid black;">{{ generate_score() }}</td>
    </tr>
    {% endfor %}
  </tbody>
</table>
</body>
</html>

Automating it and mailing the PDF’s

To make it easy I made a simple Bash script which runs the script and mails it to me as a attachment.

#!/bin/bash
TO_EMAIL=nobody@example.com
python3 main.py
weasyprint pool.html voetbalpoule.pdf
echo "Voetbalpoule" | mutt -s "Voetbalpoule $(date +'%d-%m')" -a "voetbalpoule.pdf" -- $TO_EMAIL

What is it?

PS5 RPC Client is an client I made using Python3 which will update your Discord Rich Presence with the game you’re playing on your jailbroken PS5. Requires Discord Desktop App

It requires etaHEN >= 1.4b to be running and have the following entry enabled in the /data/etaHEN/config.ini:

[Settings]
discord_rpc=1

Advised to have an static IP for your PS5.

Getting started

1. Setting up Discord

1. Go to the Discord Developers page.
2. On the top right side click ‘New Application’. Name it ‘Playstation’ or how ever you like.
3. Select the application and copy the value named ‘Application ID’ and note it down.

2. Running the client

The client will ask for the Discord Application ID and PS5 IP address upon first startup. It will write those values to a config.ini

Config values:

[settings]
client_id = '<application ID'
ps5_ip = 'xxx.xxx.x.xxx'
buttons_enabled = '1 or 0' (1 = enabled, 0 = disabled)

Windows

1. Download the latest exe release from the releases page.
2. Unzip the directory to a location of your choice.
3. Run the exe.

Linux / MacOS

1. Clone this repo
2. Install dependencies with pip3 install -r requirements.txt
3. Run python3 client.py or python client.py

Docker

1. Clone this repo, and inside the directory create a config.ini:

[settings]
client_id = 'xxxxxx'
ps5_ip = 'xxx.xxx.xxx'
buttons_enabled = 1 (enabled) or 0 (disabled)

1. Build and run the container using docker compose up -d

Ansible has a good way of storing passwords / secrets and still keeping your source code in Git. The tool is called ansible-vault and can be used to encrypt/decrypt secrets.

Creating a secret file

This is for demonstration purposes only. Use/edit our vault in case you need secrets.

Let’s say we have this Yaml file secret.yml containing a password which we want to use in our playbooks:

---
install_password: 'superPassword'

Use this command to encrypt the secret:

ansible-vault encrypt secret.yml 
New Vault password: 
Confirm New Vault password: 
Encryption successful

After this command it’s safe to share / upload it to a repository. Save the password in a password manager and you’re done.

Decrypting / viewing secrets

To view the secrets in the vault file, use the following command:

ansible-vault view <<secret file>>
Vault password: 

To decrypt it (Never upload it when you have it decrypted!):

ansible-vault decrypt <<secret file>>
Vault password: 
Decryption successful

Automatically unlocking vault

1. Command line

To prevent having to type a password every time you want to see secrets, execute the following steps:

1. Write your password to a file ~/.ansible/vault for example.

2. Set the proper permissions (600)

   chmod 600 ~/.ansible/vault
   

3. Set the following environment variable in your .bashrc

   export ANSIBLE_VAULT_PASSWORD_FILE=~/.ansible/vault
   

4. Now you can automatically unlock the vault without having the password prompt.

2. In Ansible playbooks / roles (system wide)

1. Write the password to a file /home/ansible-user/.vault for example.
2. Set the proper permissions (600)

   chmod 600 /home/ansible-user/.vault
   

3. In your ansible.cfg (located in /etc/ansible/ansible.cfg) set the following config value:

   [defaults]
   vault_password_file = /home/ansible-user/.vault
   

read -p "Namespace: " NAMESPACE
kubectl proxy &
kubectl get namespace $NAMESPACE -o json |jq '.spec = {"finalizers":[]}' >temp.json
curl -k -H "Content-Type: application/json" -X PUT --data-binary @temp.json 127.0.0.1:8001/api/v1/namespaces/$NAMESPACE/finalize

This should fix your stuck namespace.

F=<***@domain.com> R=lookuphost T=remote_smtp H=hotmail-com.olc.protection.outlook.com [104.47.14.33] X=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=yes: SMTP error from remote mail server after pipelined MAIL FROM:<***@domain.com> SIZE=165698: 550 5.7.1 Unfortunately, messages from [XX.XX.XX.XXX] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3140). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [VI1EUR04FT004.eop-eur04.prod.protection.outlook.com]

To relay the mail to an Exim SMTP server I had setup for this, allowing only access to the SMTP ports (25,465,587) by IP whitelisting, I configured the following config for Exim:

Create a new file called /etc/exim.routers.pre.conf

And configure it as following:

NOTE: If you don’t want to forward specific domains to the relay, but all, then replace domains = xxx with:

domains = ! +local_domains

This will forward all domains to your SMTP relay.

smart_route_forward:
    driver = manualroute
    domains = hotmail.com:live.nl:live.com:outlook.com:hotmail.nl
    ignore_target_hosts = 127.0.0.0/8
    condition = ${if !eq{$original_domain}{$domain}}
    condition = ${if !eq{$original_domain}{}}
    condition = "${perl{check_limits}}"
    
    transport = remote_smtp_forward_transport

    route_list = * smtprelay.domain.com::587
    no_more

smart_route:
    driver = manualroute
    domains = hotmail.com:live.nl:live.com:outlook.com:hotmail.nl
    ignore_target_hosts = 127.0.0.0/8
    condition = "${perl{check_limits}}"

    transport = remote_smtp

    route_list = * smtprelay.domain.com::587
    no_more

After this, restart the Exim service:

service exim restart