((((sandro.net))))

terça-feira, 25 de novembro de 2025

segunda-feira, 24 de novembro de 2025

Show HN: WeatherOrNot a maximal weather app in the terminal https://ift.tt/ogHGU23

Show HN: WeatherOrNot a maximal weather app in the terminal A RETRO TERMINAL WEATHER EXPERIENCE https://james-see.github.io/weatherornot/ November 24, 2025 at 03:43AM

Show HN: 3M km interferometer concept using Saturn moons https://ift.tt/zBmIRZ7

Show HN: 3M km interferometer concept using Saturn moons https://ift.tt/baPz7y2 November 23, 2025 at 11:39PM

Show HN: I built a free kids coloring site with AI https://ift.tt/pxgK61V

Show HN: I built a free kids coloring site with AI https://ift.tt/UJwH3uY November 24, 2025 at 02:36AM

Show HN: SitStand – Control your standing desk from the command line https://ift.tt/9ro8UvG

Show HN: SitStand – Control your standing desk from the command line https://ift.tt/nQrp8wW November 24, 2025 at 01:17AM

domingo, 23 de novembro de 2025

Show HN: better-env – A Secure, Developer-Friendly Alternative to .env https://ift.tt/x5gnR9P

Show HN: better-env – A Secure, Developer-Friendly Alternative to .env I’ve always hated how archaic .env files feel. Plaintext, easy to leak, and once they hit git history… you’re cooked. After accidentally committing secrets a few too many times, I finally asked myself: why don't we encrypt secrets just like passwords? So I built better-env: a local, encrypted way to manage secrets without exposing plaintext all over your machine. One place for secrets, nothing sensitive in git, your secrets get directly loaded at runtime, project-wise. It’s early, local-first, and still rough around the edges, but it already removed a whole category of stress from my workflow. I’d love feedback on whether this feels useful beyond solo devs, and what you’d want for team/CI setups. It's open source too! ( https://ift.tt/x1fErce ) https://ift.tt/hzDR7qH November 23, 2025 at 04:31AM

DJ Sandro

http://sandroxbox.listen2myradio.com