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 articleLokal.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.
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.
WATCHTOWER_LABEL_ENABLE env set to true on watchtower
com.centurylinklabs.watchtower.enable label set to true on lokal-server
LAN-Wide Accessible .local address looks like a super useful feature!
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.
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?