br4zz4:local-development

Configures subdomain-based local testing using lvh.me wildcard DNS resolution.

Updated May 25, 2025
One-click install
npx skills add https://github.com/oporpino/commons --skill br4zz4-local-development-oporpino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: br4zz4:local-development
Source: https://github.com/oporpino/commons/tree/main/ai/shared/skills/br4zz4%3Alocal-development
Command: npx skills add https://github.com/oporpino/commons --skill br4zz4-local-development-oporpino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Localhost does not expose subdomains in most browsers and frameworks, which breaks manual testing of applications that rely on subdomains or host-based multi-tenancy. ## Core Features & Use Cases - Wildcard DNS Resolution: Uses lvh.me, which resolves every subdomain to 127.0.0.1, enabling subdomain URLs against a local server. - Multi-Tenant Testing: Keeps tenant detection, host authorization, and cookie behavior consistent with production during local testing. - Use Case: When testing a Rails or Phoenix app where each account maps to a subdomain, open http://escolamagica.lvh.me:4009 instead of localhost to exercise the real host-based routing logic. ## Quick Start Ask the assistant to give you the correct lvh.me URL for testing your local app with a specific subdomain and port.

Frequently Asked Questions about br4zz4:local-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test subdomains on localhost?▼

Use lvh.me instead of localhost, since it resolves every subdomain to 127.0.0.1. Access your app at http://<subdomain>.lvh.me:<port> to test subdomain routing locally.

What is lvh.me used for in local development?▼

lvh.me is a wildcard DNS service that resolves all subdomains to 127.0.0.1. It lets developers test multi-tenant apps and host-based routing locally exactly as they behave in production.

Why does localhost not work with subdomains?▼

Most browsers and frameworks do not expose subdomains on localhost, so host-based routing and multi-tenant detection fail. A real DNS name like lvh.me preserves subdomain behavior for cookies and host authorization.

Does lvh.me work offline?▼

lvh.me requires DNS resolution, so it can fail when fully offline with an empty DNS cache. In that case, add an entry to /etc/hosts or use nip.io as an alternative.

Which port should I use with lvh.me?▼

Always use your project's actual local development port, such as the SERVER_PORT value defined in your .env file. For example, http://lvh.me:4009 for a server running on port 4009.