Daniel Ahn

Setting up Textractor w/ VNs on Linux

Wed, 04 Feb 2026 00:00:00 GMT

Setting up Textractor w/ VNs on Linux#

I’ve recently full moved over to linux and one of the things I did not set up from my windows install is Textractor used with VNs for mining cards for my Anki.

Textractor is windows only, so I took a look around for other people’s setups:

I’m currently going through ATRI right now, so running it is extremely simple. Real question is how do I get textractor to run with ATRI?

This is the script I ended up adjusting compared to the one that Mach565 made.

Proton - Experimental is what worked for me.
I used the textractor fork by https://github.com/Chenx221/Textractor
Together with exSTATIC setup described here - https://donkuri.github.io/learn-japanese/mining/#visual-novel-setup

1
#!/usr/bin/env bash
2
# This bash script makes it easy to launch Textractor and hook into Steam games
3
# Two free Japanese Visual Novels are included to provide a sample of the
4
# format. You will likely need to add your own games here unless the defaults
5
# work for every game you play and you prefer using the appid.
6
if [[ -z $1 ]]; then
7
  echo "No appid or name."
8
else
9
  # Set the default Proton and Textractor here. Typically the latest Proton
10
  # and the 32 bit version Textractor.
11
  # You can override it for a specific app if needed.
12
  proton="$HOME/.steam/steam/steamapps/common/Proton - Experimental/proton"
13
  textractor="$HOME/textractor/x86/Textractor.exe"
14
  # Set the default compat data path here (where all the wine prefixes are).
15
  # You only need to override this on a per-game basis if you install your
16
  # games on different drives.
17
  compat_data_path="$HOME/.steam/steam/steamapps/compatdata"
18
  # Default delay so the script can launc the game itself, defined here so it
19
  # can be manually adjusted if a game takes a while to start
20
  delay=5 # 20 seconds
21
  case "$1" in
22
  # If a different version of Proton/Textractor/Compat data path is needed,
23
  # make sure to include the appid in the match too,
24
  # otherwise it'll default to fallback below.
25
  "Atri" | "1230140")
26
    appid="1230140"
27
    ;;
28
  "Narcissu" | "264380")
29
    appid="264380"
30
    # Example of how to override
31
    proton="$HOME/.steam/debian-installation/steamapps/common/Proton - Experimental"
32
    textractor="/path/to/other/textractor"
33

34
    ;;
35
  # Use whatever name works for you, no need to type the full name out
36
  "Higurashi 1")
37
    appid="310360"
38
    ;;
39
  # If no other matches, fall back on using the App ID.
40
  *)
41
    appid="$1"
42
    ;;
43
  esac
44
  # compat data
45
  export STEAM_COMPAT_DATA_PATH="$compat_data_path/$appid"
46
  export WINEPREFIX="$STEAM_COMPAT_DATA_PATH/pfx"
47
  cmd=("$proton" runinprefix "$textractor")
48
  steam -applaunch $appid
49
  sleep $delay
50
  "${cmd[@]}"
51
fi

Show moreShow less

Setting up ProtonVPN with Opnsense with Ease

Thu, 29 Jan 2026 00:00:00 GMT

How to setup ProtonVPN with Opnsense using Wireguard#

You’ll need a ProtonVPN Subscription and get your WireGuard Configuration

Select

Router
Block Malware Only / Doesn’t matter
VPN Accelerator
Region of choice.

The following setup will allow you to setup an Alias that will be the list of clients you want to forward via VPN. You can do a broad network-wide setup, but that isn’t ideal with my living situation.

Create your Aliases#

Firewall → Aliases
- RFC1918
  - Type: Networks
  - Content: 192.168.0.0/16 172.16.0.0/12 10.0.0.0/8
- VPNForwarding
  - Type: Networks
  - Content: The IP Subnets you want to forward: 192.168.53.23/32 (<- if you want a specific IP) or something like 192.168.0.0/12

Configure Wireguard#

Wireguard Peer
- VPN → WireGuard → Peers
  - Click + and configure the Instance:
    - Enabled: Checked
    - Name: ProtonVPN_Peer (or similar)
    - Public Key: Copy the PublicKey from the [Peer] section of your ProtonVPN .conf file.
    - Allowed IPs: 0.0.0.0/0 (and ::/0 for IPv6 if desired). This is what the VPN server expects, but we will control the routes on the OPNsense side.
    - Endpoint Address: Copy the server address (IP or hostname) from the [Peer] section.
    - Endpoint Port: Copy the port number from the [Peer] section.
    - Keepalive: 25 (Recommended)
    - Pre-shared Key: (Optional) Copy if provided by ProtonVPN (Usually not).
- VPN → WireGuard → Instances
  - Click + and configure the Instance:
    - Enabled: Checked
    - Name: ProtonVPN_WG (or similar)
    - Private Key: Copy the PrivateKey from the [Interface] section of your ProtonVPN .conf file.
    - Public Key: Leave Empty (Will auto-populate after saving)
    - Tunnel Address: Copy the IP address/CIDR from the Address line in the [Interface] section (e.g., 10.x.x.x/32).
    - Peers: Select the Peer you created in Step 1 (ProtonVPN_Peer).
    - Disable Routes: ✓ CHECK THIS BOX. (This is essential for Policy-Based Routing/Selective Routing).

Assign WireGuard Interface and Gateway#

Interfaces → Assignments
- At the bottom, Select your wireguard Device and Add.
  - It should look something like wg0 (WireGuard - ProtonVPN_WG)
- Then go to Interfaces → Wireguard Device [ProtonVPN_WG]
- Enable Interface Checked and save.
System → Gateway → Configuration
- Click +
  - Name: Proton_VPN_GW (or similar).
  - Interface: Select the new WireGuard interface (WG_PROT_VPN).
  - Address Family: IPv4.
  - Gateway: Specify an IP address one number lower than your WireGuard Tunnel Address (e.g., if the tunnel address is 10.x.x.5/32, use 10.x.x.4). This is an arbitrary “Far Gateway” IP that OPNsense uses for routing.
    - Ignore the Far Gateway checkbox. Leave it unchecked.
  - Monitor IP: (Optional, but recommended for health check). You can use one of ProtonVPN’s DNS servers (e.g., 10.2.0.1 or 10.2.0.2 if provided in their config) or a public one like 1.1.1.1.
  - Disable Gateway Monitoring: ✓ Check this box (because the Monitor IP is not directly on the WireGuard subnet).

Firewall Rules#

LAN interface Rule
- Firewall → Rules → LAN or whatever your interface is called.
  - Action: Pass
  - Interface: OPT1 (or the interface where 192.168.3.0/24 resides)
  - Direction: In (ChatGPT told me Out, but this should be In)
  - TCP/IP Version: IPv4 (and add a separate rule for IPv6 if needed)
  - Protocol: Any
  - Source:
    - Source: **VPNForwarding** (Select the alias you created)
  - Destination:
    - Invert match: ✓ Check this box
    - Destination: **RFC1918** (This ensures local network traffic is not routed through the VPN, allowing communication with your other LAN subnets, printer, etc.)
  - Gateway: **Proton_VPN_GW** (Select the WireGuard gateway you created)
Outgoing Rule
- Firewall → NAT → Outbound. You’ll need to have Hybrid/Manual selected here.
  - Interface: **WG_PROT_VPN** (Select your WireGuard interface)
  - TCP/IP Version: IPv4
  - Protocol: Any
  - Source:
    - Source network: **VPNForwarding** (Select the alias you created)
  - Destination: Any (or if you want to be extremely specific, you can use **!RFC1918** to match the firewall rule, but Any is typically fine here).
  - Translation / Target: Interface address

Verify#

Verifiy that the IP is not your original IP.

https://whatismyip.com

Modifying list of clients using VPN.#

Go to Firewall -> Aliases and now you can modify VPNForwarding with whatever IPs you want to forward to your VPN.

You could even remove your current IP from the list to temporarily remove VPN if you want to see if your VPN is the reason why some sites don’t work.

Hopefully this guide is helpful. Thanks for reading!

Hako - A Temporary Box Storage Solution

Wed, 28 Jan 2026 00:00:00 GMT

Hako - A Temporary Box Storage Solution#

For no reason other than to make a simpler alternative to https://uguu.se/, I created Hako

Reminiscent of services like puu.sh or mixtape.moe back in the day.

I was learning how to do automated actions with Forgejo with this project, and I’ve been able to get automated builds working now. Not sure if I want to do automated deployment yet.

Multi-Instanced AdGuardHome Setup Guide

Tue, 27 Jan 2026 00:00:00 GMT

Multi-Instance Setup with Adguard Home#

I use 2 MiniPCs for this setup - https://www.amazon.com/dp/B0C89TQ1YF

Install Ubuntu 24.04 (Or whatever you want ig) and install docker.

https://docs.docker.com/engine/install/ubuntu/

On the Main AdguardHome Server#

Volumes you can change if you don’t like the defaults.
Vector is optional, this is only if you want to export the data.
Under keepalived, you need to modify KEEPALIVED_VIRTUAL_IPS to the IP that will face the clients. (separate from the ips of the individual adguardhome servers).
KEEPALIVED_UNICAST_PEERS is the list of all IPs
Double check the interface. If you’re using standard ethernet w/ Ubuntu, enp1s0 should be the default, but just check with ip addr just to make sure.

Note

If you want to make it really minimal.

You can remove everything after adguardhome section if you’re running single instance.
Remove all labels if you’re not running WUD
Keepalived is for multi-instance setup / Vector is for vector log forwarding. You can remove the ones you don’t want.

1
services:
2
    adguardhome:
3
        image: adguard/adguardhome
4
        container_name: adguardhome
5
        restart: unless-stopped
6
        volumes:
7
            - '/opt/adguardhome/work:/opt/adguardhome/work'
8
            - '/opt/adguardhome/conf:/opt/adguardhome/conf'
9
        ports:
10
            - '53:53/tcp'
11
            - '53:53/udp'
12
            # - '67:67/udp'  # This is only if you need the dhcp server, which can conflict with some linux services.
13
            # - '68:68/udp'
14
            - '80:80/tcp'
15
            - '443:443/tcp'
16
            - '443:443/udp'
17
            - '3000:3000/tcp'
18
            - '853:853/tcp'
19
            - '784:784/udp'
20
            - '853:853/udp'
21
            - '8853:8853/udp'
22
            - '5443:5443/tcp'
23
            - '5443:5443/udp'
24
        labels:
25
            - 'wud.tag.include=latest'
26
            - 'wud.watch.digest=true'
27

28
    vector:
29
        image: timberio/vector:latest-alpine
30
        restart: unless-stopped
31
        command: --config /etc/vector/vector.toml
32
        volumes:
33
            - '/opt/adguardhome/work:/opt/adguardhome/work'
34
            - '/opt/vector:/etc/vector'
35
        labels:
36
            - 'wud.tag.include=latest-alpine'
37
            - 'wud.watch.digest=true'
38

39
    keepalived:
40
        image: lettore/keepalived
41
        restart: unless-stopped
42
        network_mode: "host"
43
        cap_add:
44
            - NET_ADMIN
45
            - NET_BROADCAST
46
            - NET_RAW
47
        environment:
48
            - KEEPALIVED_STATE=MASTER  # Change this to BACKUP for subsequent instances
49
            - KEEPALIVED_VIRTUAL_IPS="192.168.5.210"
50
            - KEEPALIVED_UNICAST_PEERS="'192.168.5.211', '192.168.5.212', '192.168.5.213', '192.168.5.214', '192.168.5.215'"
51
            - KEEPALIVED_INTERFACE=enp1s0
52
            - KEEPALIVED_PASSWORD=adguard
53
            - KEEPALIVED_PRIORITY=100  # Change this value to a lower value for backup instances
54
            - KEEPALIVED_ROUTER_ID=5
55
        labels:
56
            - 'wud.tag.include=latest'
57
            - 'wud.watch.digest=true'

Show moreShow less

Save as compose.yml in your home folder

docker compose up -d then docker compose logs -f to see the logs.

You can verify if it’s working by going to http://{KEEPALIVED_VIRTUAL_IPS}:3000 and it should show the adguard UI.

On the Secondary AdguardHome Server#

This AGH server will act as the “backup” so it’ll only be in use if you’re main is down.

It’s all the same except.
- KEEPALIVED_STATE=BACKUP this needs to be set to BACKUP

1
services:
2
    adguardhome:
3
        image: adguard/adguardhome
4
        container_name: adguardhome
5
        restart: unless-stopped
6
        volumes:
7
            - '/opt/adguardhome/work:/opt/adguardhome/work'
8
            - '/opt/adguardhome/conf:/opt/adguardhome/conf'
9
        ports:
10
            - '53:53/tcp'
11
            - '53:53/udp'
12
            # - '67:67/udp'  # This is only if you need the dhcp server, which can conflict with some linux services.
13
            # - '68:68/udp'
14
            - '80:80/tcp'
15
            - '443:443/tcp'
16
            - '443:443/udp'
17
            - '3000:3000/tcp'
18
            - '853:853/tcp'
19
            - '784:784/udp'
20
            - '853:853/udp'
21
            - '8853:8853/udp'
22
            - '5443:5443/tcp'
23
            - '5443:5443/udp'
24
        labels:
25
            - 'wud.tag.include=latest'
26
            - 'wud.watch.digest=true'
27

28
    vector:
29
        image: timberio/vector:latest-alpine
30
        restart: unless-stopped
31
        command: --config /etc/vector/vector.toml
32
        volumes:
33
            - '/opt/adguardhome/work:/opt/adguardhome/work'
34
            - '/opt/vector:/etc/vector'
35
        labels:
36
            - 'wud.tag.include=latest-alpine'
37
            - 'wud.watch.digest=true'
38

39
    keepalived:
40
        image: lettore/keepalived
41
        restart: unless-stopped
42
        network_mode: "host"
43
        cap_add:
44
            - NET_ADMIN
45
            - NET_BROADCAST
46
            - NET_RAW
47
        environment:
48
            - KEEPALIVED_STATE=BACKUP  # Change this to BACKUP for subsequent instances
49
            - KEEPALIVED_VIRTUAL_IPS="192.168.5.210"
50
            - KEEPALIVED_UNICAST_PEERS="'192.168.5.211', '192.168.5.212', '192.168.5.213', '192.168.5.214', '192.168.5.215'"
51
            - KEEPALIVED_INTERFACE=enp1s0
52
            - KEEPALIVED_PASSWORD=adguard
53
            - KEEPALIVED_PRIORITY=200  # Change this value to a lower value for backup instances
54
            - KEEPALIVED_ROUTER_ID=5
55
        labels:
56
            - 'wud.tag.include=latest'
57
            - 'wud.watch.digest=true'

Show moreShow less

Save as compose.yml in your home folder

docker compose up -d then docker compose logs -f to see the logs.

Syncing the two instances together with AdGuardHome-Sync#

You’ll need to use some 3rd party to sync the two instances together.

I use the linuxserver/adguardhome-sync image

Project Link: https://github.com/bakito/adguardhome-sync
Docker Image Link: https://docs.linuxserver.io/images/docker-adguardhome-sync/

compose file probably looks something like this (not tested. just taken from my unraid instance)

1
services:
2
    adguardhomesync:
3
        image: lscr.io/linuxserver/adguardhome-sync
4
        container_name: adguardhomesync
5
        restart: unless-stopped
6
        volumes:
7
            - '/your_config_dir:/config'
8
        ports:
9
            - 8080:8080  # change this to whatever you want for the WebAPI
10
        environment:
11
            # For unraid users, but change it to whatever works for you.
12
            - PUID=99
13
            - PGID=100
14
            - UMASK=022
15
            - CONFIGFILE=/config/adguardhome-sync.yaml

Show moreShow less

You can either run this on your master instance, but I run it on a separate machine from the DNS servers.

Either append it to your already existing compose file (minus the services:) or just make a new compose file and you can run with docker compose -f filename.yml up -d

You’ll probably need to read the docs for an up-to-date for the config. Mine looks like this javascript

1
# cron expression to run in daemon mode. (default; "" = runs only once)
2
cron: "*/10 * * * *"
3

4
origin:
5
  # url of the origin instance
6
  url: http://{first_instance_ip}
7
  # apiPath: define an api path if other than "/control"
8
  # insecureSkipVerify: true # disable tls check
9
  username: admin
10
  password: password
11

12

13
# replicas instances (optional, if more than one)
14
replicas:
15
  - url: http://{second_instance_ip}
16
    username: adminSkip
17
    password: password
18

19
# Configure the sync API server, disabled if api port is 0
20
api:
21
  # Port, default 8080
22
  port: 8080
23
  # if username and password are defined, basic auth is applied to the sync API
24
  username: username
25
  password: password

Show moreShow less

Save as adguardhome-sync.yaml under the config dir you’re using.

vector.toml#

Note

you do not need this if you don’t use vector.

If you want to use vector to export data to like a influxdb, greptimedb, etc, this is what mine looks like

1
data_dir = "/etc/vector/data"
2

3

4
[sources.adguardfile]
5
type = "file"
6
include = ["/opt/adguardhome/work/data/querylog.json"]
7

8
[sinks.vector]
9
type = "vector"
10
inputs = ["adguardfile"]
11
address = "ADDRESS OF YOUR OTHER VECTOR INSTANCE RETRIEVING THIS DATA"

On the main vector server, i have this (you can adjust everything to make it fit to however you wan to setup

1
[sources.adguardhome]
2
type = "vector"
3
address = "0.0.0.0:9001"
4

5
[transforms.vector_to_json]
6
type = "remap"
7
inputs = ["adguardhome"]
8
source = """
9
. = parse_json!(string!(.message))
10
.T = replace!(.T, "Z", "+00:00")
11
.timestamp = parse_timestamp!(.T, "%FT%T%.9f%:z")
12
del(.T)
13

14
.IP_24 = parse_regex!(.IP, r'(?P<number>\\d+.\\d+.\\d+.?)').number + "x"
15
.TLD = parse_regex(.QH, r'^.*?(?P<tld>[^.]+.[^.]+)$').tld ?? ""
16

17
.Result = object(.Result) ?? {}
18
if length(.Result) != 0 {
19
    .Reason = get(.Result, ["Reason"]) ?? null
20
} else {
21
    .Reason = null
22
}
23
del(.OrigAnswer)
24
del(.Result)
25
"""
26

27
[sinks....] # You need some sort of sink to go to.

Show moreShow less

FAQ#

Why use keepalived? There’s Primary/Secondary DNS on my Router.#

https://superuser.com/questions/462926/how-do-preferred-and-alternate-or-multiple-dns-servers-work
Basically, the behavior of that “primary/secondary” is completely up to the client.
- Router sends the primary/secondary information to the client, but what the client does with that information is totally up to the client and a lot of times aren’t properly implemented.
- When it decides to failover, when it decides to failback, when it decides to even use the secondary DNS is up to the client. And this varies a lot. For example, a lot of TVs don’t even bother using the secondary. Some clients don’t even store the secondary DNS IP. Windows (at least from when I tried) doesn’t even failover within a reasonable amount of time if at all, and the failback is unpredictable.
Keepalived will properly tell the router whether to use the primary/secondary based on whether they’re able to ping each other or not.

What to set as my Virtual/Machine IPs?#

It is better to assign these from your router. Set the MAC Address to be statically assigned an IP, rather than trying to set this up from the machine’s side. It’s way more easily maintainable this way.
You’ll also want to make sure your DHCP server does not assign IPs in the range of static assignments. Most routers these days should be smart enough to not do that, but I would just do it just in case.
- For example. My DHCP server will assign 192.168.5.10 - 192.168.5.200. It will not assign anything in that 192.168.5.201 -192.168.5.255 which I can use for static assignments.

Why use docker?#

Docker will isolate the environment that AGH runs and remove any dynamic dependencies between AGH and the system. The only time things might break is if Docker has some issue, but that is way smaller of a blast radius than installing it directly.
It’s way easier to deploy. Once you have your compose file, you can just repeatedly deploy pretty easily.
- If you use something like Arcane/Portainer, you can use GitOps feature to then sync with a git repo (although you’d probably want to either make the IPs more dynamically configured for privacy or use a private/onprem repo).

`permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.51/images/lettore/keepalived/json": dial unix /var/run/docker.sock: connect: permission denied`#

You need to run with sudo
You can make it not require sudo by adding to the docker group https://docs.docker.com/engine/install/linux-postinstall/

What filters do you use? (Filters → DNS blocklists)#

Adguard’s default one
https://github.com/hagezi/dns-blocklists
- Hagezi DNS Blocklist Pro++
- Hagezi DNS Blocklist TIF
https://oisd.nl/
- OISD NSFW

Basic Adguard Guide#

Basically the main thing is filters → Custom filtering rules
- Do @@||{domain_name}^$important if you want to whitelist something
- Do ||{domain_name} to block a new thing.

DoH/DoT#

My setup is the following
- Upstream DNS Servers set to https://dns.cloudflare.com/dns-query
- Load-Balancing
- Bootstrap DNS servers is set to 1.1.1.1 and 1.0.0.1 (without this, your dns will not work when coming back online unless you have a DNS leak somewhere.
- Private reverse DNS servers set to your router’s address.
- Use Private reverse DNS resolvers - True
- Enable reverse resolving of clients IP addresses - True
/etc/resolv.conf (not inside docker, but on the host) looks like

Terminal window

1
domain lan
2
search lan
3
nameserver {KEEPALIVED_VIRTUAL_IPS}

AdGuardHomeStats

Some clients are not using AdguardDNS#

This is probably due to either 1) the client hardcoded the DNS (common with a lot of TVs/IoT in particular) or 2) it hasn’t refreshed DHCP yet, so it hasn’t gotten the new DNS IPs from your router.
Solving the Hardcoded DNS problem.
- Best way is to redirect all outgoing requests to port 53 to force them to go to your adguard instance.
- You’ll need to figure this out with your own router, but here’s my OPNSense configuration
  
  OPNSense

Load-Balancing servers rather than Primary/Backup#

Probably have to use something like HAProxy

DNS Certificate / Using a domain for adguard / Setting custom domain to resolve locally when on local network.#

TBD if there’s interest.

Auto-Updating Everything#

To auto-update the apt sequence, I don’t have a good solution yet. Most simple is probably just some cron job or smth. I think there’s an auto updater for apt now idk
To auto-update the containers, I’m currently using Arcane which is similar to portainer, which has an auto-update feature.
Can also use something like WUD. Don’t use watchtower that’s long gone.

Alternatively…. you can update manually yourself

Terminal window

1
sudo apt update && sudo apt upgrade -y
2
sudo docker compose pull && sudo docker compose down && sudo docker compose up -d

Want to try my new vibe-coded project?#

https://github.com/NekoShinobi/blocked-agh

Basically a way to check if an address is blocked or not, and it doesn’t require authentication. And the user can then request to have it unblocked.

My experience with AGH vs PiHole (old. back when i migrated)#

So far, I do like AGH a lot more for my simplistic use cases. Having DoH/DoT supported out of the box is a billion times more convenient than having to setup all these complicated workarounds to make DoH work with each provider. Even if I provided a solution for Cloudflare, it would not necessarily translate to using a different DoH network.
PiHole’s UI has come a long way and had a lot of improvements over the past year. However, it’s still very much lacking from AGH’s fast and responsive UI.
AGH is missing client groups and an easier way to manage groups of users rather than having to manually enter one at a time. This is not really something I personally utilize, so it’s not a dealbreaker for me.
AGH’s way of handling wildcard DNS Rewrites is so much better than PiHole’s manual entry. It’s so annoying and unclear on how a not-so-experienced user does this on PiHole.
AGH has a weird UX with allow/blocklists. It has way too many modals and loading screens just to do a simple entry for a list. I wish this was just one page that handled it, and allowed a way to edit multiple entries at once like how PiHole did it.
AGH’s approach to custom filtering lists is something PiHole does a lot better. AGH approaches it as a product where they expect the user to be already familiar with the style of how AdGuard or uBlock creates custom lists. However, they really should have this as an advanced feature, and have a more user-friendly version of this as the front page.

Why You Should Use Valkey Instead of Redis

Tue, 27 Jan 2026 00:00:00 GMT

What Happened to Redis?#

Redis for a long time was provided under the BSD License, which basically meant people could do whatever they wanted as long as they kept the License copy and attributions. Several other licensing changes happened over the year, but the big one was in 2024, where they relicensed 7.4 with RSAL and SSPL.

This left people hesitant to continue using Redis because people who write proprietary code probably would find it cumbersome to have to rewrite code in a way that isn’t proprietary because the license forces people to contribute back to the project.

It also restricts commercial use entirely, which meant that big companies were most likely not going to be contributing back at all anymore, and perhaps moving to better solutions.

Dismissing Redis to Simplify the Stack#

A good number of projects also realized that using Redis wasn’t really necessary for their needs. As PostgreSQL improves in performance over the years, people started to even use it as a Time Series Database.

Rise of Valkey#

valkey-io

valkey

Waiting for api.github.com...

00K

Waiting...

Valkey rose after the introduction of the new licenses, and it was created in a way to be very simple to migrate from an existing instance… unless you were someone like me who didn’t bother doing it until redis 8.

Here’s a list of projects that I now have moved over to using valkey (even if they do not support it explicitly)

https://github.com/LogicLabs-OU/OpenArchiver

1
Make sure to use REDIS_PASSWORD to set the password.

https://github.com/immich-app/immich

1
Use REDIS_DBINDEX to set the db_num of your instance.

https://github.com/Freika/dawarich

1
Set REDIS_URL without the db_num
2

3
Then set
4
RAILS_CACHE_DB
5
RAILS_JOB_QUEUE_DB
6
RAILS_WS_DB
7

8
to the db num you want to use.

https://github.com/nextcloud/server

1
In your php config, it'll look something like this
2
$CONFIG = array (
3
  'memcache.local' => '\\OC\\Memcache\\APCu',
4
  'memcache.distributed' => '\\OC\\Memcache\\Redis',
5
  'memcache.locking' => '\\OC\\Memcache\\Redis',
6
  'redis' =>
7
  array (
8
    'host' => 'valkey',
9
    'port' => 6379,
10
    'password' => 'password',
11
    'dbindex' => 5,
12
  ),
13
...

https://github.com/outline/outline

1
Set REDIS_URL to redis://:password@valkey:6379/{db_num}

Daniel Ahn

Setting up Textractor w/ VNs on Linux

Setting up Textractor w/ VNs on Linux#

Setting up ProtonVPN with Opnsense with Ease

How to setup ProtonVPN with Opnsense using Wireguard#

Create your Aliases#

Configure Wireguard#

Assign WireGuard Interface and Gateway#

Firewall Rules#

Verify#

Modifying list of clients using VPN.#

Hako - A Temporary Box Storage Solution

Hako - A Temporary Box Storage Solution#

Multi-Instanced AdGuardHome Setup Guide

Multi-Instance Setup with Adguard Home#

On the Main AdguardHome Server#

On the Secondary AdguardHome Server#

Syncing the two instances together with AdGuardHome-Sync#

vector.toml#

FAQ#

Why use keepalived? There’s Primary/Secondary DNS on my Router.#

What to set as my Virtual/Machine IPs?#

Why use docker?#

permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.51/images/lettore/keepalived/json": dial unix /var/run/docker.sock: connect: permission denied#

What filters do you use? (Filters → DNS blocklists)#

Basic Adguard Guide#

DoH/DoT#

Some clients are not using AdguardDNS#

Load-Balancing servers rather than Primary/Backup#

DNS Certificate / Using a domain for adguard / Setting custom domain to resolve locally when on local network.#

Auto-Updating Everything#

Want to try my new vibe-coded project?#

My experience with AGH vs PiHole (old. back when i migrated)#

Why You Should Use Valkey Instead of Redis

What Happened to Redis?#

Dismissing Redis to Simplify the Stack#

Rise of Valkey#

`permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.51/images/lettore/keepalived/json": dial unix /var/run/docker.sock: connect: permission denied`#