A Free AWS Console for MiniStack, ZFS Regrets, and a Browser-Based SQL IDE

Homelab Highlights for 2026-10-05: self-hosting and homelab notes worth knowing.

[Audio embed placeholder]

The Lead: Free AWS Console for MiniStack - docker-compose up and done

A new open-source web UI for MiniStack, the free AWS emulator, provides full CRUD for S3, DynamoDB, Lambda, SQS, Cognito, SES, SNS, and Secrets Manager. It runs via Docker Compose, includes MCP server integration for AI assistants, and claims significant performance improvements through FalkorDB caching.

Why it matters: For homelab operators and developers using local AWS emulation, this fills the gap left by MiniStack’s lack of a web interface and LocalStack’s paid tiers, offering a free, self-hosted alternative with broad service coverage.

Source: github.com

News Roundup

7 ZFS Things I Wish I’d Known Before Using It on Proxmox

A practical guide covering common ZFS pitfalls on Proxmox, including default record size causing write amplification for small files, ARC memory starvation on systems with less than 64GB RAM, and the importance of setting the correct ashift value for modern drives.

Why it matters: ZFS is the default storage option for many Proxmox users, and these misconfigurations can silently degrade performance or waste resources. Knowing them before setting up a pool saves hours of troubleshooting.

Source: Virtualization Howto

Jellyfin is free and beautiful, but Plex does one thing that keeps me paying

An honest comparison: Jellyfin is preferred for its open-source nature and features, but Plex’s seamless remote access for non-technical users—without requiring VPN, Tailscale, or reverse proxy setup—is the single reason the author maintains a subscription.

Why it matters: For homelab operators who share media with family or friends, the remote access friction is a real tradeoff. This article clarifies the cost-benefit decision between full control and ease of use.

Source: XDA - Self-Hosting

This Proxmox Restore Portal Helps You Find the File You Actually Need

A web-based tool that mounts Proxmox backups (PBS and vzdump) and allows browsing, searching, and downloading individual files without restoring the entire VM. It supports incremental backups and version selection by date.

Why it matters: Restoring a whole VM just to retrieve a single config file is wasteful and slow. This portal provides a targeted, time-saving alternative for granular file recovery.

Source: Virtualization Howto

MCP for agent-to-agent comms may be the riskiest protocol you’ve never heard of

A researcher found that the Model Context Protocol (MCP) used by AI agents from Google, JP Morgan Chase, Rapid7, and others has a structural trust flaw: a compromised agent can pass malicious instructions to other agents, which execute them because they trust the source. Mitigation is difficult and not yet addressed.

Why it matters: As AI agents become more common in enterprise and homelab environments, this vulnerability represents a fundamental security risk that could allow lateral movement and unintended actions across agent networks.

Source: Security - Ars Technica

Tool & Software Highlight: LibreDB Studio: open-source, free, self-hosted SQL IDE that runs in your browser, for 46 databases

A free, MIT-licensed SQL IDE that runs as a Docker container, providing browser-based management for 46 database engines including PostgreSQL, MySQL, MongoDB, Redis, ClickHouse, and DuckDB. Features include SSO via OpenID Connect, role-based access, an AI assistant that can use local Ollama models, and read-only agent enforcement at the database level.

Why it matters: For homelabs with multiple database types, this eliminates the need to expose ports or install desktop clients, centralizing management in one secure, self-hosted interface with strong community trust signals from official database project listings.

Source: github.com

Community Highlight: What AI coding tools work well for native Windows desktop development and GUI debugging?

A developer building a Windows desktop utility with Tauri, Vue/TypeScript, and Rust asks which AI coding tools are effective for native Windows development and GUI debugging, noting that web-focused tools often struggle with native window handling.

Why it matters: The Tauri+Rust stack is increasingly used in self-hosted projects, and the challenge of finding AI tools that handle both Rust and TypeScript, plus native Windows debugging, is a common pain point. The thread offers real-world experiences for others facing the same stack.

Source: r/ChatGPTCoding - top (day)

Sources

Transcript

Host A: Welcome to Homelab Highlights, the show that surfaces practical homelab wins and useful self-hosted tools.

Host A: Kicking off with a project that showed up over the weekend: a web console for MiniStack, the free open-source AWS emulator. The person behind it says the whole reason it exists is that MiniStack has no web interface at all, and the obvious alternative, LocalStack, put its web UI behind a paid tier that runs from forty-nine dollars a month up to four hundred twenty-nine. So they built their own and shipped it as a Docker Compose stack. One command and it is up on port three thousand.

Host B: And the feature list is surprisingly broad for something three days old. It covers full create, read, update, and delete for S3, DynamoDB, Lambda, SQS, Cognito, SES, SNS, and Secrets Manager. That is most of what a local development stack actually touches. There is also real-time resource discovery and multi-tenant support, so it can manage several isolated environments at once, which sounds handy if a team shares one box.

Host A: Two things in the announcement stand out. First, the performance claim: the author says DynamoDB queries that took forty-three seconds now return in under a tenth of a second, thanks to caching in FalkorDB, a graph database. That is the author’s own benchmark, so worth taking with a grain of salt, but the architecture idea is sound. Second, there is an MCP server built in, meaning an AI assistant like Claude can query the local AWS environment directly. For anyone already experimenting with agents against cloud APIs, testing against a local emulator instead of a real bill is a genuinely appealing setup.

Host B: Fair caveats, though. A community bot flagged that the repository is only days old, so this is early-stage software by any measure, and the roadmap lists EC2, RDS, IAM, and CloudWatch as still to come. It is MIT licensed and the author says free forever, and screenshots and docs are in the repo. For a homelab, the fit is simple: run it on the same Docker network as MiniStack, point the browser at it, and stop poking at the emulator through the CLI. Worth a look if local AWS development is part of the week.

Host A: Next up, a piece from Virtualization Howto titled seven ZFS things the author wishes had been known before running it on Proxmox. ZFS is a native storage type in Proxmox, so plenty of homelab operators default to it, and the article walks through the gotchas that only show up after the pool exists. The headline lesson for anyone about to build a pool: read this before picking record sizes, ARC tuning, and replication choices, not after. One specific gotcha: the author mentions that default record size of 128K can cause massive write amplification for small-file workloads like mail servers or git repos, and tuning it down to 16K or even 4K for those datasets can cut write overhead by half. Another is that ARC on a system with less than 64GB of RAM can actually hurt performance if left at defaults, because it starves other processes. The article also covers why you should never use the default ashift value on modern drives, and how to check it before creating the pool.

Host B: On the media server front, an XDA piece makes an honest argument: Jellyfin is free, open source, and the writer genuinely prefers it, but Plex does one thing that keeps a subscription alive. The subheading says it plainly: friends should not need to understand the network. Remote access for non-technical users is the whole tradeoff, and that is a real cost to weigh, not a knock on Jellyfin. The article goes into detail about how Plex’s relay service and automatic remote access just work without any port forwarding or reverse proxy setup, while Jellyfin requires either a VPN, a Tailscale network, or a properly configured reverse proxy with SSL. For a homelab operator who is the sole user, Jellyfin wins every time, but for sharing with family who just want to click a link, the friction is real.

Host A: Also from Virtualization Howto, a look at a Proxmox restore portal aimed at the restore nobody talks about: not the whole-VM rebuild, but finding the one file actually needed inside a backup. Anyone who has restored an entire virtual machine to fish out a single config file knows exactly why that deserves a better interface. The portal provides a web-based file browser that mounts the backup and lets you browse the filesystem, search by filename, and download individual files without restoring the whole VM. It supports both PBS and vzdump backups, and can even mount incremental backups to find the version of a file from a specific date. That is a quality-of-life improvement that saves hours.

Host B: One security note to leave with, from Ars Technica. A researcher tested AI agents from Google, JP Morgan Chase, Rapid7, and two government agencies and found a structural flaw in MCP, the protocol agents use to talk to each other. A compromised agent can pass malicious instructions down the chain, and the next agent follows them because it trusts the source. Hard to mitigate, apparently by design. If agents are running anywhere on the network, that article is worth ten minutes. The researcher demonstrated a scenario where an agent tasked with reading email was tricked into executing a command that deleted files, because the malicious instruction came from another agent that the system trusted. The fix would require a fundamental redesign of how agents authenticate each other’s outputs, which is not on any roadmap yet.

Host A: Tool highlight time, and this one is a good fit for anyone whose homelab has quietly accumulated a database zoo. LibreDB Studio is a free, MIT-licensed SQL IDE that runs as a Docker container and opens in the browser. The pitch is that the databases never need a port exposed, no SSH tunnels, nothing installed on the laptop. It sits on the same Docker network as the database containers and connects by service name, so only the editor is reachable and the data stays internal.

Host B: The coverage is the headline. Eighteen built-in drivers, from PostgreSQL and MySQL to MongoDB, Redis, ClickHouse, DuckDB, and Elasticsearch, plus twenty-eight more engines that speak those wire protocols, like MariaDB, Valkey, and CockroachDB. The maintainers publish a compatibility table that says honestly how much works on each engine, which is a refreshing change from vague claims. And twelve database projects, including PostgreSQL, Redis, and ClickHouse, list it in their own official docs after reviewing it. That is a decent trust signal before a weekend gets spent on it.

Host A: Two setup notes from the project’s own write-up. Saved connections live in browser local storage by default, which is fine for a quick look but not for a lab used from multiple devices, so switching the storage provider to SQLite with a mounted volume is the recommended day-one change, along with setting the admin password and JWT secret explicitly. On the identity side, it supports OpenID Connect, so Authentik or Keycloak users get single sign-on, with an admin and a read-only user role. There is also an AI assistant, off until a model is configured, and it can point at a local Ollama so both model and data stay on home hardware. The agent is read-only enforced at the database level, not by a text filter, and it never applies its own suggestions. That seems like the right way to build it.

Host B: Community highlight, and this one is a question rather than a war story. Over on the ChatGPT Coding subreddit, a developer is building a native Windows desktop utility with a mixed stack: Tauri with Vue and TypeScript for the management UI, and Rust for the backend. The question is which AI coding tools actually hold up for native Windows desktop development and GUI debugging, which is a fair ask, because web-focused tooling tends to fall apart the moment a bug lives in native window handling.

Host A: It is a good question for this audience, because the Tauri-plus-Rust combination is showing up in more self-hosted dashboard and utility projects. The honest answer from the thread’s framing is that the mixed stack is the hard part: the tool has to be competent in Rust, in TypeScript, and in whatever the Windows GUI debugging workflow looks like, and few are equally strong across all three. Anyone who has shipped something similar, the thread is open, and experiences there are one person’s results rather than a benchmark, but the pattern of web tooling struggling with native debugging comes up often enough to be worth planning around.

Host A: That’s Homelab Highlights for Monday. Until next time, happy hosting!