Ooh, I will look into that. Thanks! Never used azure and it's still not cheap, but much more reasonable

I'm in doubt on whether I should just self sign my app for the service verification I want to do. Signing with a trusted cert can always still be done when I get some (payed) users

Yeah, I don't get why they can't do it like apple: Register with a (small) fee with a creditcard or with some small verification; Trust the certificate. Revoke the certificate and never hand you another one if you betray the trust...

Now it's just another money machine for 3rd party cert providers

If anyone has tips to do it cheaper, please let me know ;)

I wanted to sign my code so that I can verify it from a service to make sure not every app on the computer can contact the service and do certain administrator actions without verification

getlode.app Streamline your local development flow with instant SSL protected .test domains

If you want to check it out; Join the beta on getlode.app

You'll receive a mail when it's publicly downloadable (currently working on the mails 😅)

If you find out, let me know since I'm also building a developer focused tool, and trying to figure out the same thing ;)

Try to not focus on the features of your product. Instead try to focus on what pains a user experiences which are solved by your tool

Which I now spot a typo in... Damn, let's try that again 🙈

Today I'm starting on the MVP for Lode (getlode.app) after finishing the landing page this morning (Last step was the opengraph meta/image).

I actually develop on macOS, but no matter your OS, localhost is not a good replica. The blogpost describes what kind of differences you can expect though. One example would be how browsers handle cookies differently for localhost

If you're interested in a all in one solution, the tool I'm building will help with this. You can always subscribe on the landing page I'm building. (it's not finished, but subscribing works...)

Check it out at getlode.app

By promoting on certain reddit communities, by writing blog posts and trying to get those in the right spots, and also by trying to get my SEO in good order (will be more longterm though)

I use it through a locally resolved .test TLD 😉 That's why I can test locally as if it is in production

For just the website (as long as it doesn't have any functionality besides marketing) I simply run it locally during development, and go straight to production (hosted on Cloudflare).

I was writing a blogpost about why you shouldn't use localhost during development directly.

My current title is "Stop using localhost: bugs it creates and how to prevent them"

I actually just submitted it in the hopes of getting it published on 'Level Up Coding' on Medium

I think buildinpublic is more about sharing what you do, or where you're going, and not about sharing details about the how. You shouldn't show how your secret sauce works, just show what results that sauce delivers.

User data wise; just don't share those. Only global stats.