July 17th, 2024

Show HN: I made a tool to HTTPS your localhost

Lokal.so simplifies local development with features like sharing localhost publicly, debugging data, AI assistant, self-hosted tunnel server, Cloudflare integration, JSON conversion, edge location customization, and more. It offers a comprehensive solution for developers.

Read original articleLink Icon
Show HN: I made a tool to HTTPS your localhost

Lokal.so is a tool designed to simplify local development by offering various features. It allows users to share their localhost with a public and https .local address, debug incoming data, replay without triggering real WebHooks, and develop with the assistance of an AI-powered assistant. The platform provides a self-hosted Lokal Tunnel Server for freedom and privacy, Cloudflare Ephemeral Tunnel for faster site delivery, an AI Assistant, unlimited .local domain access, S3 built-in server, JSON to language scheme conversion, and more. Users can also customize their edge location for minimum latency and access Lokal through web, desktop, and CLI interfaces. Additionally, Lokal offers features like JSON prettifying, file sharing, tunnel creation automation, live inspection, API gateway usage, and more. The tool caters to developers looking for a comprehensive solution for local development, multi-device usage, and remote team collaboration, with pricing plans tailored to different needs.

Link Icon 16 comments
By @peterldowns - 4 months
Congratulations on the launch! How does the remote -> local tunneling work? The docs you linked are a little unclear to me.

How does this differ from something like Localcan, which seems to offer the same features? https://www.localcan.com/

For what it's worth, I'll mention that I have an open-source application, Localias [0], that does the same local https development + mDNS support for HTTP/TCP/UDP traffic. Localias doesn't support traffic inspection or remote -> local tunneling, but it's open source, built on caddy, and works on mac/linux/wsl2. It's a statically built binary and you can share your configs with your whole dev team in your git repo.

[0] https://github.com/peterldowns/localias

By @brrrrrm - 4 months
Why not just self sign a local cert? Its really easy to do (ask an AI for a relevant example in your language of choice)
By @cwt137 - 4 months
This product seems similar to Ngrok and some other solutions. How does this product differentiate itself from everyone else?
By @asadhaider - 4 months
Shouldn't the watchtower docker config be configured to only monitor and update the lokal-server container and not every container on the host?

WATCHTOWER_LABEL_ENABLE env set to true on watchtower

com.centurylinklabs.watchtower.enable label set to true on lokal-server

By @mrzool - 4 months
You lost me at "AI assistant help".
By @ghoshbishakh - 4 months
Congratulations! We all know how difficult it is to launch a working product. Looks like you are trying something similar to what we do at https://pinggy.io/

LAN-Wide Accessible .local address looks like a super useful feature!

By @rcarmo - 4 months
Won't this break Bonjour/Zeroconf .local announcements from hosts? Should you be using .local at all?
By @jmull - 4 months
Looks good.

I've been using Cloudflare's thing ("tunnel", I think) for the basic functionality, but I see this does additional things. If I ever want to do those things (or I just decide I want to try something different) I'll keep this in mind.

By @radeeyate - 4 months
What all can the "AI Assistant" do?
By @difosfor - 4 months
Intriguing, but I think VS Code's built in GitHub tunneling support is enough for me.
By @efilife - 4 months
The page is blank for me. Fennec on android
By @pxue - 4 months
Too. many. features
By @zuzuleinen - 4 months
Great video!
By @terryds - 4 months
congrats on the launch!
By @ptspts - 4 months
After looking at your web page and your HN post for 1 minute each, I have no clue what your software is doig, where it is running, whether it is open source, how much a subscription costs etc.

It's also confusing to me that the title says HTTPS, the post says HTTP.

The use of HTTPS in the HN post title as a verb makes it incomprehensible for me. Are you planning an HTTPS-basef network attack on the computers of all HN users? Probably not. But then why do you suggest it in the title? Why not write a title which is easy to understand, using common verbs?