Dino
1.9K posts








GitHub's performance in 2013. The web used to be so fast.

Introducing Slipway 🐙 I moved all my production apps from a PaaS to Hetzner + Coolify. The economics were obvious — way more power for a fraction of the cost. But after running Coolify for a while, I wasn't satisfied with it in terms of UX and some weird behaviours. It's generic. It doesn't know what a Sails app is. It doesn't understand Waterline models, or why you might want to run await User.find() against production at 2am when something breaks. So I built Slipway — an open-source, self-hosted platform purpose-built for Sails.js. Here's what it does: Deploy — slipway slide does zero-downtime blue-green deployments. Your users never see downtime. Helm — A production REPL right in the browser. Query models, run helpers, inspect config. No more SSH + docker exec. Think Tinkerwell and Guppy Bridge — Auto-generated data management from your Waterline models. Like Laravel Nova or AdminJS but zero configuration. Dock — SQL console, schema diff, and one-click migrations. No more manually writing ALTER TABLE statements for production. Quest — Job dashboard for sails-hook-quest. View, pause, resume, trigger jobs from the UI. Lookout — Infrastructure monitoring via sails-hook-slipway telemetry. Backups — One-click database backups to S3/R2 with one-click restore. Total memory footprint: ~120MB. Compare that to Coolify's ~800MB-1GB. The CLI is zero-dependency. The entire platform uses execFile() for every Docker command — shell injection is impossible by design. Laravel developers have had Forge, Nova, Tinker, and Horizon for years. Now Sails and The Boring JavaScript Stack developers have Slipway. Open source. MIT license. One command to install. Read the blog post: blog.sailscasts.com/introducing-sl… Start on GitHub: github.com/sailscastshq/s… Check out the docs: docs.sailscasts.com/slipway





















