11–20 of 24 posts
> Recently I wasted several hours wrangling my dev environment only to find out that the browser frontend was talking to the wrong version of the backend. I have never faced this problem even though I hard-code the port. It's because I run the server program through VS Code's debugger. If there's already a session, it would warn me.
Wild to vibe code something in a week then charge $50/month for it. I understand servers cost money but lol there’s no way the costs are that high. Also insane the amount of code generated here.
> Recently I wasted several hours wrangling my dev environment only to find out that the browser frontend was talking to the wrong version of the backend. I have never faced this problem even though I hard-code the port. It's because I run the server program through VS Code's debugger. If there's already a session, it would warn me.
Well, there's your problem! You're not getting the efficiency gains of multi-agent slop slinging loops working like that…
> why on earth are we still using simple numbers to describe which process to connect to? Why not use names instead. Not super popular, but: https://en.wikipedia.org/wiki/SRV_record
You will need to run
sysctl net.ipv4.ip_unprivileged_port_start=80
Wild to vibe code something in a week then charge $50/month for it. I understand servers cost money but lol there’s no way the costs are that high. Also insane the amount of code generated here.
The part that is being charged for isn't the coding, but the operating. How little should someone charge to be on pagerduty 24/7?
Also I couldn't find anything saying what "priority support" actually involves. The terms have a generic intent to reply in 2 business days note, but nothing about what kind of coverage the different tiers get or guarantee someone is actually going to respond to the pager 24/7 if something wonky happens in the cloud.
It's not much extra work to do this technique (tunnel to publicly accessible domain name from locally or privately hosted setup) with cloudflare tunnels. It's also completely free, all you need is a domain name managed by cloudflare (~10 bucks a year).
You just throw up a cloudflared container (can be part of your local docker compose stack), it will serve whatever you like from that local system at the public domain name - no port forwarding, no IP configuration, just works, over private VPN tunnel.
I use this all the time for personal projects:
> https://developers.cloudflare.com/tunnel/
Unlimited cloud tunnels for 49 dollars a month is not that great - you can have up to 1000 tunnels on the free cloudflare plan, which I'm realistically never going to max out. Once you've done it once, it's a handful of lines to paste into any future compose stack with your Cloudflare API key to use again, it's incredibly simple to use, and will do the same automatic HTTPS setup.