HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
peterldowns
localias
Go2023–2026
peterldowns / localias

localias

custom local domain aliases for local dev servers

8Distinct people
14Mentions
0Explicit recommenders
1.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

custom local domain aliases for local dev servers

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 4:35:25 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year14 dated mentions

Observed mentions: 2023-05-19 20:42:47 UTC to 2026-05-01 07:14:43 UTC.

0123452023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC312
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC505
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC413
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

3 sources
Pretty good overview from Baldur — I don't always agree with everything he writes but this seems relatively correct. One question I'd ask him (and anyone else reading) is: what are some other options for monetization? Over the last few weeks I had three different VCs reach out to me about some of the open source projects I've been releasing, and ask me if I'd thought about making a business out of them. I told them that no, based on the problem the software was solving, I didn't see how I could adopt open-core or companion-saas business models, and I wasn't sure how else it could be done while keeping the code open source. Can anyone suggest a viable business model that would allow: * Code remains at least source available, ideally open source for non-commercial use. * I can charge for commercial use. * Actually doing the licensing is rea
Read the rest
sonable, ie no spyware or phoning home from the tool. Wouldn't need to be perfect, I understand that if the code is open source a company could easily fork and use it without paying me. The idea would be to make it zero-headache to pay me for a license if the code is being used by a funded team. The projects: * https://github.com/peterldowns/localias * https://github.com/peterldowns/pgmigrate
In Free and open source software projects are in transition

Show HN: Localias, securely manage local devserver aliases

Hey HN, Localias is a new tool that you can use to securely manage your local development servers. Use localias to securely proxy a local development server running on http://localhost:3000 and access it at https://frontend.test. Localias is built on top of Caddy, so it's secure and performant. And because it's built on top of Caddy, it will automatically generate and install a custom root certificate, and automatically generate and sign certificates for each of your aliases. This all works by editing your /etc/hosts file and generating a Caddy config, then running the proxy server for you either in the foreground or as a daemon. It's easier to deal with than running Caddy yourself. Your whole team can share a configuration file in your git repo, making it easier to share URLs with each other while developing. I hope you try it out and fi
Read the rest
nd it useful! The code is MIT-licensed and I'm happy to accept any feedback, feature requests, PRs, or comments. Have a good weekend, Peter
11 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.