> Forget editing /etc/hosts or typing 192.168.0.12! Instead, pay $19 (instead of $29!) excl. VAT for a service that does this for you! God damn, I hate this industry.
hate? for something that saves more than it costs?
Show HN: Local development with .local domains and HTTPS
41–50 of 108 posts
Re: Show HN: Local development with .local domains and HTTPS
#42Can recommend https://github.com/FiloSottile/mkcert for this purpose (local development certs).
I'm a big fan of mkcert for local HTTPS cert generation.
I just setup a local https dev domain wildcard (*.internal) with mkcert and caddy a few days ago - working great on all my devices and only took a few hours to figure out and get working.
Re: Show HN: Local development with .local domains and HTTPS
#43Looks like an interesting project. What I guess is not really clear is why you'd want to do TLS for local only connections? Are the services published with the .local domain accessible from outside as well so it's like a ngrok alternative? I'm pretty sure I'm misunderstanding the value-add of having TLS for localhost connections...
Certain browser features/apis are only available when in a secure context https://www.digicert.com/blog/https-only-features-in-browser... so I imagine this might be a reason you would want it. That being said I don't know why you would pay for an application that does this but I guess I'm not the target market.
Yep. A lot of OAuth integrations will refuse to work on HTTP, too. Some have a `localhost` exception to that restriction, but not all.
Re: Show HN: Local development with .local domains and HTTPS
#44> Forget editing /etc/hosts or typing 192.168.0.12! Instead, pay $19 (instead of $29!) excl. VAT for a service that does this for you! God damn, I hate this industry.
Well, it does a little more than that. You can type yourservice.local instead of 192.168.0.12:1234.
I don't know that I'd buy this if I still had a mac, but I do think that paying for quality of life improvements can be worthwhile. For example, I do pay for a license of IntelliJ idea, even though VSCode costs $0, and I'm not even a full-time software dev.
Re: Show HN: Local development with .local domains and HTTPS
#45Isn't that just a sidecar? Maybe Kubernetes is hard enough that some engineers are willing to pay $19 to avoid using it.
Re: Show HN: Local development with .local domains and HTTPS
#46This submission violates the HN guidelines: "Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity." https://news.ycombinator.com/newsguidelines.html
The https://news.ycombinator.com/user?id=jarekceborski account was created 1 day ago, the only submission is this one https://news.ycombinator.com/user?id=jarekceborski and the only comments are on this submission https://news.ycombinator.com/threads?id=jarekceborski
Re: Show HN: Local development with .local domains and HTTPS
#47Looks like an interesting project. What I guess is not really clear is why you'd want to do TLS for local only connections? Are the services published with the .local domain accessible from outside as well so it's like a ngrok alternative? I'm pretty sure I'm misunderstanding the value-add of having TLS for localhost connections...
TLS is easy enough... I'm just not sure why one would want or need a certificate authority involved with local connections other than to get rid of the nag screen in Firefox or Chrome.
Mkcert makes it easy, why not?
Re: Show HN: Local development with .local domains and HTTPS
#48Forget editing /etc/hosts Why?
Might not be able to, if you're looking to test out something on a mobile device, or a school/work device that's locked down.
Re: Show HN: Local development with .local domains and HTTPS
#49You can do this with Caddy already, with Automatic HTTPS. Caddy will automatically set up its own CA and use it to issue certs (using smallstep) with .local and .localhost domains. We don't do anything with mDNS though but we've thought about it; none of us use macs anymore but PRs are welcome to make that work. I don't have enough expertise with mDNS to confidently implement it myself, and especially less-so because…
.local is usually setup if you have an mDNS daemon running. I think Ubuntu does this ootb, and if you still have an old windows install, you may have a copy of 'bonjoir' that was bundled with iTunes. You could probably lean on existing software to do most of the work.
I agree that reaching out to systemd-resolved on Linux and Bonjour on Mac/Windows is probably the way to go, but I don't have the time/energy to learn these APIs and test it right now, hence why I'm asking for help! :)
Re: Show HN: Local development with .local domains and HTTPS
#50Lets introduce proprietary service with a payment plan. That will simplify things LOL. Just switch to Linux and you will never ever had to deal with this weird stuff agian!
Just to be fair: it seems it has no "payment plan", but a one-time payment.