The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Minimal, no-JS web forum software
Hello HN!<p>I've found my SQL knowledge to be lacking, so I made a project that uses SQLite as a backend.<p>As it is intended for self-hosting I aim to make it easy to set up and maintain. Getting it up & running takes no more than a few commands (bar setting up a proxy such as nginx, which is out of scope).<p>I've set up a "demo" site at <a href="https://forum.agreper.com/" rel="nofollow">https://forum.agreper.com/</a> if you want to try out the UI.
Show HN: I built a site that lets users find playlists by songs they contain
Show HN: I built a site that lets users find playlists by songs they contain
Show HN: I built a site that lets users find playlists by songs they contain
Show HN: I built a site that finds the cheapest place to buy a book
Show HN: I built a site that finds the cheapest place to buy a book
Show HN: I built a site that finds the cheapest place to buy a book
Show HN: If Spotify and Tinder Had a Baby
Show HN: Fractal Garden – An Exhibition of Mathematical Beauty
Show HN: Fractal Garden – An Exhibition of Mathematical Beauty
Show HN: Maiao, Stacked Diffs for GitHub
Show HN: Maiao, Stacked Diffs for GitHub
Show HN: I wrote a short story about von Neumann probes
Show HN: I wrote a short story about von Neumann probes
Show HN: I developed an app that creates interactive product demos in minutes
Show HN: I developed an app that creates interactive product demos in minutes
Show HN: Garnix, fast and easy CI for Nix
Hello HN!<p>For the past few months, I've been building a Nix-specific CI service, and quite a few people have been productively using it, so I thought I'd Show HN it.<p>You might be wondering why build a Nix-specific CI. It turns out its quite hard to get a really good CI setup for Nix without spending a lot of time or money on it (or both), and even then solutions don't tend to be optimal.<p>Garnix, on the other hand, handles everything, and simply. Just create an account, install the GitHub app on the repositories you want, and you're good to go! Each package gets its own GitHub check, and separate log output, which makes it really easy to figure out what went wrong (you can see an example here: <a href="https://garnix.io/build/X9knYZOB" rel="nofollow">https://garnix.io/build/X9knYZOB</a>). Builds are very fast compared to e.g Github Actions. The build artifacts are made available in a Nix cache so you never have to rebuild locally. And there are builders for x86-64 Linux as well as M1 Macs and aarch64 Linux.<p>Try it out: <a href="https://garnix.io" rel="nofollow">https://garnix.io</a>. It's free, though if you like it, consider donating! (Note that it only works with flakes.)<p>Cheers,
Julian
Show HN: Garnix, fast and easy CI for Nix
Hello HN!<p>For the past few months, I've been building a Nix-specific CI service, and quite a few people have been productively using it, so I thought I'd Show HN it.<p>You might be wondering why build a Nix-specific CI. It turns out its quite hard to get a really good CI setup for Nix without spending a lot of time or money on it (or both), and even then solutions don't tend to be optimal.<p>Garnix, on the other hand, handles everything, and simply. Just create an account, install the GitHub app on the repositories you want, and you're good to go! Each package gets its own GitHub check, and separate log output, which makes it really easy to figure out what went wrong (you can see an example here: <a href="https://garnix.io/build/X9knYZOB" rel="nofollow">https://garnix.io/build/X9knYZOB</a>). Builds are very fast compared to e.g Github Actions. The build artifacts are made available in a Nix cache so you never have to rebuild locally. And there are builders for x86-64 Linux as well as M1 Macs and aarch64 Linux.<p>Try it out: <a href="https://garnix.io" rel="nofollow">https://garnix.io</a>. It's free, though if you like it, consider donating! (Note that it only works with flakes.)<p>Cheers,
Julian
Show HN: Garnix, fast and easy CI for Nix
Hello HN!<p>For the past few months, I've been building a Nix-specific CI service, and quite a few people have been productively using it, so I thought I'd Show HN it.<p>You might be wondering why build a Nix-specific CI. It turns out its quite hard to get a really good CI setup for Nix without spending a lot of time or money on it (or both), and even then solutions don't tend to be optimal.<p>Garnix, on the other hand, handles everything, and simply. Just create an account, install the GitHub app on the repositories you want, and you're good to go! Each package gets its own GitHub check, and separate log output, which makes it really easy to figure out what went wrong (you can see an example here: <a href="https://garnix.io/build/X9knYZOB" rel="nofollow">https://garnix.io/build/X9knYZOB</a>). Builds are very fast compared to e.g Github Actions. The build artifacts are made available in a Nix cache so you never have to rebuild locally. And there are builders for x86-64 Linux as well as M1 Macs and aarch64 Linux.<p>Try it out: <a href="https://garnix.io" rel="nofollow">https://garnix.io</a>. It's free, though if you like it, consider donating! (Note that it only works with flakes.)<p>Cheers,
Julian
Show HN: Reflame – Deploy your React web apps in milliseconds
Hi HN! I've been working on Reflame since I quit my job at Brex last year, excited to finally open it up for everybody to try out! Here's a demo: <a href="https://www.youtube.com/watch?v=SohUnrjiIxk" rel="nofollow">https://www.youtube.com/watch?v=SohUnrjiIxk</a><p>Reflame deploys client-rendered React web apps instantly, to previews and to production.<p>In concrete wall-clock terms, deploys generally take:<p>- ~50-500ms from our VSCode extension<p>- ~500-3000ms from our GitHub app<p>(Jump to this comment (<a href="https://news.ycombinator.com/item?id=33134082" rel="nofollow">https://news.ycombinator.com/item?id=33134082</a>) for what makes Reflame so fast)<p>The Reflame GitHub App automatically deploys default branches to production, and other branches to previews. If you've used Netlify/Vercel's GitHub apps, you should feel right at home. The difference is it’s multiple orders of magnitudes faster. Fast enough that <i>you'll probably never see an in-progress deploy on GitHub ever again</i>, only ready-to-go preview/production links.<p>No more having to babysit builds or having to context switch to and from other tasks before being able to see our changes deployed in previews or production. Previewing, sharing, and even shipping, can now become part of the so-called inner loop, giving us the superpower to stay in flow state for much longer.<p>The Reflame VSCode extension is yet another order of magnitude faster than even the GitHub App. It was designed to offer an experience that can rival local development workflows in both speed and ergonomics, while addressing many of local dev's limitations around collaboration and production-parity. Every time we make a change (e.g. by saving a file), the extension will deploy that change (in ~50-500ms) to a "Live Preview", and will immediately update the app in our browsers to reflect that change.<p>Live Previews can operate in one of two modes:<p>- Development mode delivers updates through React Fast Refresh, offering the familiar state-preserving instant feedback loop we know and love from local development workflows.<p>- Production mode delivers updates by triggering a full browser reload on every change, and in exchange for this extra bit of friction, we get to develop against a byte-identical version of the fully optimized production deployment that customers will see once we ship, with a tighter feedback loop than was ever possible before.<p>Live Previews deliver updates over the internet, meaning we can effortlessly test out our changes on multiple devices simultaneously, and show our changes to anyone in the world, just by sharing a Live Preview link, all while having our updates reflected automatically across all connected devices in real-time (with live reload or React Fast Refresh <i>over the internet</i>).<p>Being able to ship quickly is valuable on its own, but Reflame's true north star has always been to enable customers to ship quickly <i>with confidence</i>.<p>One way Reflame helps customers ship with more confidence today is by making previews with full production-parity available at every step of the development process. Previews in Reflame are accessible at the exact same URL customers will use to access the production deployment, instead of at a different subdomain for each preview (i.e. every preview is accessed through <a href="https://reflame.app" rel="nofollow">https://reflame.app</a> instead of at <a href="https://some-branch-of-reflamedotapp.reflame-previews.dev" rel="nofollow">https://some-branch-of-reflamedotapp.reflame-previews.dev</a>). Behind the scenes, this is implemented using session cookies that our CDN will check to determine which version of the app to serve.<p>This is only the tip of the iceberg. We have some really exciting prototypes around testing and typechecking that we've been exploring that could allow us to ship with even more confidence <i>without ever slowing us down</i>.<p>If any of this sounds interesting for the apps you're building or planning to build (taking into account this comment (<a href="https://news.ycombinator.com/item?id=33134092" rel="nofollow">https://news.ycombinator.com/item?id=33134092</a>) below describing what Reflame is not well suited for), please sign up and give it a try!<p>I can't wait to see what you’ll build with it! :)