The inline code formatting is making my eyes bleed....
Lcl.host: fast, easy HTTPS in your local dev environment
81–90 of 101 posts
Re: Lcl.host: fast, easy HTTPS in your local dev environment
#82Were some bugs that show only in the https version of the app?
HTTP/2 quirks, e.g. header capitalization.
I think I've seen some different cache behaviors.
Secure cookies (and maybe same/cross site stuff?)
Re: Lcl.host: fast, easy HTTPS in your local dev environment
#83I've been using mkcert for ages now for local development. Free, open source, and works offline.
Why use any service for this?
Re: Lcl.host: fast, easy HTTPS in your local dev environment
#84Earlier quoted context omitted.
Sorry about that, we're working on switching this to a warning and not an error, that slipped by us before release. After the next update, it will only show a warning if you're not on the latest release.
We just released a fix for the version error, this will be the last one you see, we promise!
Thanks. The upgrade command v0.0.15 gives didn’t work for me. In fact the only method I found that would successfully update was to uninstall it, then untap your tap, then reinstall.
Also, I echo the other people saying that the typeface you chose for the website is very difficult to read.
Re: Lcl.host: fast, easy HTTPS in your local dev environment
#85Earlier quoted context omitted.
you're completely free to run firefox from 5 years ago and it will not refuse to run.
No, you are not. Mozilla bricked SSL certificates that are mandatory for everything, including Browser Extensions. There is a flag for about:config to unbrick it. Problem is though, that this lasts less than a second because of the remote settings service running in a loop. If you block that services domain with a host firewall (like opensnitch), Firefox will do an endless for loop using 100% CPU load trying to reque…
Just for the fun I went to https://ftp.mozilla.org/pub/firefox/releases/53.0/linux-x86_... and downloaded Firefox 53 from 2017.
Font are ugly but it loaded HN just fine.
Re: Lcl.host: fast, easy HTTPS in your local dev environment
#86I like the interactive setup. I think this is solid but if you want something even faster and easier to use, try my project localias [0]. The parent project, lcl.host, has some annoying restrictions: > This CA has some restrictions though: it can only issue certificates for subdomains of lcl.host and localhost, but that’s all you need for local development. Localias, on the other hand, lets you use any custom domain…
>This CA has some restrictions though: it can only issue certificates for subdomains of lcl.host and localhost, but that’s all you need for local development.
This sound like a security feature, not (just) an annoying restriction. Though an attack model for a local CA is a bit flimsy.
Re: Lcl.host: fast, easy HTTPS in your local dev environment
#87Earlier quoted context omitted.
This would be perfect if combined with Traefik's method of config via docker tags.
The Caddy Docker Proxy Module enables Caddy to act as reverse proxy for docker containers via labels: https://github.com/lucaslorentz/caddy-docker-proxy
Whoa, thanks. I had my eye on Caddy for a local reverse proxy but can't be doing with maintaining another big config file. With the labels method the reverse proxy becomes "set and forget" and you're probably going to be editing bundled compose files to get rid of port conflicts anyway (or using override like https://blog.gpkb.org/posts/multiple-web-projects-traefik/)
Re: Lcl.host: fast, easy HTTPS in your local dev environment
#88Earlier quoted context omitted.
No, you are not. Mozilla bricked SSL certificates that are mandatory for everything, including Browser Extensions. There is a flag for about:config to unbrick it. Problem is though, that this lasts less than a second because of the remote settings service running in a loop. If you block that services domain with a host firewall (like opensnitch), Firefox will do an endless for loop using 100% CPU load trying to reque…
Just for the fun I went to https://ftp.mozilla.org/pub/firefox/releases/53.0/linux-x86_... and downloaded Firefox 53 from 2017. Font are ugly but it loaded HN just fine.
> you're completely free to run firefox from 5 years ago
> Firefox 53 from 2017
not the same. I was talking about post-quantum Firefox releases, which added the mentioned dependencies on Mozilla's SSL certificate.
(The grandparent's comment was also about post-quantum, obviously)
Re: Lcl.host: fast, easy HTTPS in your local dev environment
#89They lost me at "Signin to Anchor.dev".
Re: Lcl.host: fast, easy HTTPS in your local dev environment
#90Earlier quoted context omitted.
Just for the fun I went to https://ftp.mozilla.org/pub/firefox/releases/53.0/linux-x86_... and downloaded Firefox 53 from 2017. Font are ugly but it loaded HN just fine.
> you're completely free to run firefox from 5 years ago > Firefox 53 from 2017 not the same. I was talking about post-quantum Firefox releases, which added the mentioned dependencies on Mozilla's SSL certificate. (The grandparent's comment was also about post-quantum, obviously)
The grandparent post is about some malicious tactic used by Mozilla to prevent you from using old Firefox releases. I think it's pretty clear that there isn't such intent - if there was, the very least Mozilla would have done is preventing you from downloading old versions from their own servers. Having a few specific releases that broke over time doesn't mean anyone is trying to stop you from using an older version of Firefox. It's basically called software.