CoderLuii projects

Open tools.For builders.

Self-hosted software from a cybersecurity engineer who builds what he needs. Find something you can use.

4: Shipped projects
261,860: Docker pulls across 3 images
2,667: GitHub stars across 3 repositories

CoderLuiiIndependent software and experimentsSource and public work

I work in cybersecurity. Outside of that, I build tools for things that annoy me or take too much time. Some of them end up here.

Have a look around. If something is useful to you, try it. If something is broken, tell me.

Illustration of CoderLuii coding at three monitors with Peanut asleep beside the desk

A message from CoderLuii

I’ve been messing with computers since I was a kid. Games, Photoshop, websites, editing videos, streaming. If it had a screen, I wanted to figure it out.

Eventually I got tired of doing the same things manually. I wanted to build something useful instead of doing the same work again tomorrow.

ChannelWatch started because I wanted better monitoring for my own DVR. I learned Python and Docker along the way. Broke things, fixed them, kept going. Then other people started using it too.

The name CoderLuii came during one of those late build sessions. I had three monitors, the news on the right, and a terminal on the left. I needed a handle for my first public repository. Coder described what I was becoming, and Luii was already mine. It stuck.

I’m still learning as I go. I like making things, sharing what works, and talking to people who are into the same stuff. If one of these tools saves you some time, that makes me happy.

Tools in the workshop

Python
TypeScript
PowerShell
Bash
C++
Java
Docker
OpenCode
Git
Astro
Tailwind
Node.js
Cloudflare

See a problem become a workflow

A dashboard is useful when it helps you decide what to do next. Here are three parts of a ChannelWatch workflow: recognizing a warning, choosing notifications, and investigating delivery or health issues.

Spot a problem

Compare activity and DVR health on the dashboard, then inspect the warning state.

ChannelWatch dashboard with active streams, upcoming recordings, disk usage, activity timeline and multi-DVR health. — ChannelWatch · Dashboard overview

ChannelWatch dashboard showing illustrative stale DVR freshness and disk pressure warnings. — ChannelWatch · Dashboard warning state

Choose what needs your attention

Choose disk-space thresholds and route notifications for each DVR from the same web UI.

ChannelWatch disk alert settings with percentage and gigabyte thresholds and per-DVR controls. — ChannelWatch · Disk alert thresholds

ChannelWatch routing matrix with per-DVR destinations for channel, recording, VOD and disk alerts. — ChannelWatch · Notification routing

Check what happened next

Inspect notification delivery and review DVR health when something needs attention.

ChannelWatch delivery log with sent and retry states, channel, event type, payload size and receiver errors. — ChannelWatch · Notification delivery log

ChannelWatch diagnostics with health checks, multi-DVR status, logs, alert tests and debug bundle controls. — ChannelWatch · Health and diagnostics

Watch the sample walkthrough

Sample walkthrough: review DVR activity and storage, inspect disk alerts and notification routing, then open the delivery log and diagnostics. These are simulated interface states; no notifications are sent.

ChannelWatch interface captures with illustrative sample data. Select a screenshot for the full-size view. These are separate examples, not a recorded end-to-end incident. Explore ChannelWatch

Choose your workspace.

Start with the coding workflow you prefer and where you want it to run.

Three ways to set up a coding workspace
Project	Choose it when	Your part
HolyCode Visit site ↗Source ↗	You want OpenCode in a Docker workspace.	Run Docker and configure your provider.
HolyCode Cloud Visit site ↗	You want a hosted Linux workspace with several coding CLIs.	Choose a paid workspace and configure your tools.
HolyClaude Visit site ↗Source ↗	You prefer Claude Code with a browser interface.	Run Docker and configure your provider.

Check each project’s documentation for current setup and authentication requirements.

Already using Channels DVR?

ChannelWatch is the monitoring tool shown above.

ChannelWatch site ↗Source ↗

Taking shape

Two projects in development.

Dubvox
Waitlist
Voice-preserving AI dubbing for translating uploaded audio into another language.
- AI
- Voice Cloning
- Translation
Join Waitlist
Sacris
Waitlist
Catholic Discord bot for daily readings, saints, prayers, Rosary support, liturgical calendars, and examination tools.
- Discord
- Faith
- Community
Join Waitlist

Two projects taking shape, with their own sites and waitlists.

The work, in the open.

Public repository stars and image downloads refresh automatically. Stars are not a user count, and Docker pulls include automated and repeat downloads.

Repository stars and Docker pulls
Project	GitHub stars	Docker pulls
HolyCode	65GitHub	20,881Docker Hub
HolyClaude	2,579GitHub	215,808Docker Hub
ChannelWatch	23GitHub	25,171Docker Hub

Follow the work

HolyCodeReleases Issues
HolyClaudeReleases Issues
ChannelWatchReleases Issues

What you run and maintain

A container packages a workspace, but you still choose where it runs and how it is accessed. Local Docker gives you control of the host. A hosted workspace moves that host elsewhere and adds a subscription.

Persistence matters because a working environment includes more than installed tools. Keep workspace files and configuration on the storage documented by each project, and check what survives a restart before relying on it.

For monitoring, the dashboard is one part of the path: the DVR must be reachable, and notification destinations need their own configuration. A delivery record and a health check answer different questions.

Use the project documentation for supported configuration. Keep credentials and private data out of screenshots, shared workspaces, and public bug reports.

Help shape the next fix

A useful bug report starts with what you tried, what you expected, and what happened instead. Add the project version and a small example that someone else can reproduce.

For a feature request, describe the job you are trying to finish and where the current workflow gets in your way. That context is more useful than a list of buttons to add.

Credits

Built and maintained by CoderLuii, with feedback from the people trying the projects and contributing in the open.

PROJECT SOURCESCoderLuii on GitHubDocumentation, releases, and issue trackers live with each project.

Build with CoderLuii today

The projects are here to use, inspect, and build on. Explore the source on GitHub, join other builders on Discord, and follow the next release on X. If the tools help you, you can support the work and help fund what comes next.

Source code