Hey Hunters! All of us here at Anchor are absolutely stoked to be releasing lcl.host, a new developer tool, to all of you absolutely free! 🚀 lcl.host is the absolute fastest ⚡️ and easiest 😌 way to get HTTPS setup in your development environment 🖥️. Once the Anchor CLI toolchain is installed simply run `anchor lcl` from the root of your application/project/service and we take care of the rest. It is truly that easy, give it a try for yourself. In a terminal run `brew install anchordotdev/tap/anchor` and `anchor lcl` from the root of your project. The toolchain automatically handles the following for you: ✅ Configures your local certificate stores to trust Anchor-provided certificates from your account, and your account only. ✅ Detects the application name and language/server type, then provisions the application's service and resources through Anchor's API. ✅ Provisions a certificate for your app (or service), and writes the certificate and key pair to files in your application directory. You can then use this certificate to manually enable HTTPS/TLS in your development environment. ✅ Adds WebPKI-quality certificates to your filesystem that are specific to your app or service. ✅ Finally, the Anchor Setup Guide shows you a few easy steps to set up and use ACME for future certificate provisioning. So you don’t have to ❌ configure DNS ❌ edit /etc/hosts ❌ run complicated openssl commands ❌ worry about expiring certificates ❌ manage local truststores This is my dev environment, which doesn’t have any sensitive data in it, should I really run HTTPS locally? While dev/prod parity should be enough to want to run HTTPS locally (i.e. you want your browser to run in a truly secure context, always) there are a number of reasons that you might be required to run HTTPS while in development! Mixed Content ⚠️ CORS Errors ⛔️ HTTP/2👩‍💻 Secure Cookies 🍪 OAuth and secure 3rd Party endpoints 🎁 Localhost Apps and Marketplaces 💹 Requirement for tools 🔨 📣 We really appreciate any feedback you have for us. What do you want to see next from the team? 🎉 To celebrate our launch we’ll be giving a special, hand-crafted, gift to a limited number of early adopters!

Reviews of lcl.host

Jonan Scheffler

•1 review

Local HTTPS is horrible to set up. Now I get to ignore it and I'm never going back.

Report

1yr ago

Mark Turner

lcl.host

•2 reviews

(Biased: I help work on lcl.host) It's very very very nice to have real TLS from the start to the end of a project. Doing actual HTTP/3(QUIC) with real TLS and catching CORS issues on my box without any complicated tooling/setup is pretty dope. I'm doing some Go-based MTLS right now and it's been a breeze getting all the cert bits wired up. Kudos.

Report

1yr ago

Jesse Robbins

•3 reviews

If you work local first & want to be local secure, this = ❤️

Report

1yr ago

View all 4 reviews

Chris Stolt

Maker

📌

@victoria_wu Easy as pie ;-)

Gabe Moronta

Visla

@stolt45 Nicely done, good job, and can't beat the price! Wish you all the success!

Tanvir Hasan

Sugary

@stolt45 can we connect on likedin

Yash Jejani

Realm App

@stolt45 Congrats on the launch, Chris.

@mogabr Thanks, Gabe.

Rami

Go Mail Merge

💡 Bright idea

I'll definitely need this in the future. it will help me test webhooks with Stripe and other providers so I can avoid using the Stripe CLI during development!

@kingromstar Thanks, Rami. lcl.host doesn't currently support ingress to your dev environment. But sounds like that'd be something you need?

Joep van den Bogaert

voam

This is great! There is always a point where this becomes an issue 😅 awesome to have a simple and fast solution. Thanks for this!

@jopie Thanks, Joep 😀 Let us know if you have any feedback or need a hand with anything.

@stolt45 Will do!

lcl.host

Get HTTPS in your local dev environment

Do you use lcl.host?

Review lcl.host?

Reviews of lcl.host