Forget editing /etc/hosts Why?
Cause you pay then not 19$, but you want to pay, did you not know this?
Show HN: Local development with .local domains and HTTPS
31–40 of 108 posts
Re: Show HN: Local development with .local domains and HTTPS
#32I'm curious about the license requirements. Is it 1 license per install, or 1 per install that is currently serving? I have two devices, but I will never use them at the same time (and if I do by accident, I'd expect your software to stop working).
It's perpetual license. So you can enter the license key on a new device and it will automatically deactivate previous device.
Re: Show HN: Local development with .local domains and HTTPS
#33Earlier quoted context omitted.
Android supports it now. https://source.android.com/docs/core/ota/modular-system/dns-...
Do you mean that this issue report can now be considered as resolved? https://issuetracker.google.com/issues/140786115 I'd love to update my notes if that's the case.
I don't know anything more than the docs I linked to.
Re: Show HN: Local development with .local domains and HTTPS
#34> 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.
When I read this comment I knew it must be targeting MacOS users. The only reason I clicked the link is to confirm my assumption. Edit: I'm not trying to shame MacOS users. I'm just saying that Linux and MacOS users (Windows users don't use /etc/hosts so out of discussion) have very different behaviour regarding paying for software.
I mean, the creator's personal website exactly looks like the Apple website and he's selling clones of Apple wallpapers, too.
Re: Show HN: Local development with .local domains and HTTPS
#35Lets 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!
Re: Show HN: Local development with .local domains and HTTPS
#36> 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.
What could you possibly hate about this?
$19 is only a couple minutes worth of engineering labour.
This is actually useful if you're running multiple servers on your network and don't want to remember the IPs of every single one of them. And not having to set up HTTPS for every single one of them is a plus.
Re: Show HN: Local development with .local domains and HTTPS
#37You 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.
Re: Show HN: Local development with .local domains and HTTPS
#38This is my poor man's, do-it-yourself, LAN development with HTTPS method:
https://doc-kurento.readthedocs.io/en/latest/knowledge/selfs...
Should probably be a blog post. Would be happy to get comments on improvements or updates to the explained process. For now, I already gathered that Android seems to have finally added mDNS resolution support, which is nice as a whole Note banner can then be removed from that page. I also took note that maybe the whole thing can be simplified greatly with Caddy, albeit I think that getting into explaining mkcert is useful for readers who are new to that stuff and don't know how to generate their own SSL certs (like myself a month before writing all that).
Re: Show HN: Local development with .local domains and HTTPS
#39Regarding the certs. Does this do something special to trust the self-signed root certificate that you add? or do you need to manually trust it on any device that you use to connect to this? I assume that's the case, but want to check I understand correctly.
You need to manually trust on each device. There is a button for that in the app, that shows the Trust certificate dialog. For other devices it quit easy, e.g. you can AirDrop RootCA.pem into the iPhone or iPad.
Re: Show HN: Local development with .local domains and HTTPS
#40> 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.
And sometimes I hate the HN comment section.
Obviously you’re not paying $19 for hosts file editing. Obviously! SSL cert generation is a pain in the ass, a tool that automates all of that for you is a valid tool. And I find the mDNS stuff really interesting, I do a lot of testing on mobile devices and connecting to my dev server from a phone can be really annoying.
If you don’t like the price that’s fine: don’t pay it. The market will decide whether this price is appropriate or not. An independent developer has made a tool that scratches their personal itch and made it available for others to use for a fee. And gets heaped with scorn for it. This place is an absolute cesspit sometimes.