You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Home Assistant Blueprint for ZEN37 800LR - zwavejs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Softrender backend for Dear ImGui, as well as examples for SDL2 and WinAPI.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
First home lab, start to finish: Proxmox VE + TrueNAS + media stack. Beginner walkthrough with every command explained (Sept 2026).
From spare computer to home lab: Proxmox + TrueNAS, start to finish
What this is: a build-it-yourself guide for turning one or two old computers into a proper home lab: virtual machines, containers, a shared storage box your whole house can use, and a full media library stack (Jellyfin, the download manager apps, and where the files come from), plus how to reach it from outside your house safely.
Who this is for: you have an old desktop or two, you can follow instructions, and you have never touched a hypervisor. No Linux experience assumed. Every command and every screen is explained, and each step tells you what you should see before you move on.
Time: about 1 hour for the first box (Proxmox), 45 minutes for the storage box (TrueNAS), plus however long your data takes to copy. Most of it is waiting.
The single most important thing in this guide: give every box a fixed IP address so it never moves. Everything else you can fix later by reading a screen. If a machine changes address,
iptv-org -> Dispatcharr -> Jellyfin: US channel lineup with a self-updating guide (verified Sept 2026)
iptv-org → Dispatcharr → Jellyfin — the complete hand-held walkthrough
What you end up with: a US TV channel lineup in Jellyfin, with a program guide that fills itself in every night, without you touching it again.
Who this is for: you've heard of Docker and Jellyfin but have never touched Dispatcharr. No Linux wizardry assumed. Every command is explained, and every step tells you what you should see before you continue.
Time: 30 minutes for a working setup (Quick Path), 60–90 minutes if you also build your own guide grabber (Proper Path). Most of that is waiting.
Difficulty: copy-paste. If a step ever looks wrong, stop and read the box under it — the failure modes are all covered.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I've recently launched a tool that wraps many of the commands here with a user interface. This desktop application is currently available for macOS. There's a roadmap outlining planned features for the near future.
Feel free to request any features you'd like to see, and I'll prioritize them accordingly.
One of the most important aspects of this application is that every command executed behind the scenes is displayed in a special log section. This allows you to see exactly what’s happening and learn from it.
Here's the link to the repository: https://github.com/Pulimet/ADBugger
App Description:
ADBugger is a desktop tool designed for debugging and QA of Android devices and emulators. It simplifies testing, debugging, and performance analysis by offering device management, automated testing, log analysis, and remote control capabilities. This ensures smooth app performance across various setups.
Noise: Unity editor has lots of temporary files that we don’t want git to track
Broken object references: Unity keeps track of objects created by using random GUIDs, and if they aren’t tracked using .meta files then there can be conflicts that really break your project
Unresolvable merge conflicts: files like scene files that are written in confusing languages (like YAML) that are supposed to be translations of Unity editor actions into code. Most likely, you cannot resolve using Git, and the only way to resolve merge conflicts is to open it in a text editor and resolve them manually while hoping you don't mess anything up because these files are confusing and not meant to be manipulated directly.
Large files: Sometimes assets are large and take up a lot of storage space
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Control lights with a Philips Hue Dimmer Switch (only RWL020 (US) and RWL021 (EU), RWL022, the one that says 'hue' on the bottom, has a different button layout.)
This blueprint is a simplified version of stefanroelofs's `ZHA - Philis Hue Dimmer Switch V2', but this one has no default inputs and with full configuration available. This makes the remote easily configurable for purposes other than controlling lights.
If you are intending to just use it for use as a light switch, I recommend using his blueprint, which you can find at https://gist.github.com/stefanroelofs/775e2e0a3cdb3d72a9451fb247492d59
It includes customizable 'on' button behaviour and default setup of the dimmer buttons to dim as they normally would. To make the configuration available for other automations, I had to remove these very useful functionalities.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
The core idea
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
Deploy & secure a Next.js app + Postgres DB on a VPS
Self-Hosting Next.js Tutorial
Follow the instructions below to deploy a Next.js app with a local PostgreSQL database to a VPS, secure it, and connect it to a custom domain with free SSL. Watch the accompanying tutorial on YouTube: https://www.youtube.com/watch?v=2T_Dx7YgBFw
Instructions & commands:
Get your VPS server on Hostinger (Use code CODINGINFLOW for 10% off). Install Ubuntu 24 as the OS and set a root password.
Log into your server as root: ssh root@<your-server-ip>
Update Linux packages: apt update && apt upgrade -y