| You are Manus, an AI agent created by the Manus team. | |
| You excel at the following tasks: | |
| 1. Information gathering, fact-checking, and documentation | |
| 2. Data processing, analysis, and visualization | |
| 3. Writing multi-chapter articles and in-depth research reports | |
| 4. Creating websites, applications, and tools | |
| 5. Using programming to solve various problems beyond development | |
| 6. Various tasks that can be accomplished using computers and the internet |
| #!/usr/bin/env python3 | |
| # ------------------------------------------------------------------ | |
| # Script Name: Audiogenipy | |
| # Description: A Python Script to Create an Audiobook | |
| # from a Text File using Python and gTTS. | |
| # Website: https://gist.github.com/ostechnix | |
| # Version: 1.0 | |
| # Usage: python audiogenipy.py | |
| # ------------------------------------------------------------------ |
| #!/data/data/com.termux/files/usr/bin/bash | |
| install_udocker(){ | |
| apt update | |
| yes | pkg install -y python-pip patch proot | |
| if pip freeze | grep -Eq "^udocker=="; then | |
| pip uninstall -y udocker |
This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1
This gist is almost entirely not unlike Derek Seaman's awesome blog:
Proxmox VE 8: Windows 11 vGPU (VT-d) Passthrough with Intel Alder Lake
As such please refer to that for pictures, here i will capture the command lines I used as i sequence the commands a little differently so it makes more logic to me.
This gists assumes you are not running ZFS and are not passing any other PCIE devices (as both of these can require addtional steps - see Derek's blog for more info)
Note:i made no changes to the BIOS defaults on the Intel Nuc 13th Gen. This just worked as-is.
| #!/bin/bash | |
| # Constants | |
| DEFGRUB="/etc/default/grub" | |
| KLCMDL="/etc/kernel/cmdline" | |
| MODULES_CONF="/etc/modules" | |
| I915_SRIOV_DIR="$HOME/i915-sriov-dkms" | |
| pause() { | |
| read -s -n1 -p "Press any key to continue ... " |
this gist is part of this series
This assumes you are running Proxmox 8.2 and that the line source /etc/network/interfaces.d/* is at the end of the interfaces file (this is automatically added to both new and upgraded installations of Proxmox 8.2).
This changes the previous file design thanks to @NRGNet for the suggestions to move thunderbolt settings to a file in /etc/network/interfaces.d it makes the system much more reliable in general, more maintainable esp for folks using IPv4 on the private cluster network (i still recommend the use of the IPv6 FC00 network you will see in these docs)
This one is the one that has to work, even more so the domain controllers. This is what my swarm looks like
you may want to read from the bottom up as later migrations are where i had the process more locked and less experimentation
So the plan is as follows (and is based on my experience with home assistant oddlye enough)
Part of collection: Hyper-converged Homelab with Proxmox
Update 09-10-2024: I have moved on to a setup with Docker LXC on Proxmox, with bind-mounts (without VirtioFS) as described in Gist Docker Swarm in Vm's with CephFS.
Update 07-03-2025: The Dockge LXC does this even better, eliminating most issues, with the Docker LXC](https://community-scripts.github.io/ProxmoxVE/scripts?id=docker)!
| #!/bin/bash | |
| # Raspberry Pi ZRAM script | |
| # Tuned for quad core, 1 GB RAM models | |
| # put me in /etc/init.d/zram.sh and make me executable | |
| # then run "sudo update-rc.d zram.sh defaults" | |
| modprobe zram | |
| echo 3 >/sys/devices/virtual/block/zram0/max_comp_streams | |
| echo lz4 >/sys/devices/virtual/block/zram0/comp_algorithm |