rellm

I’m in the midst of reviving https://beatscratch.io (https://github.com/falrm/BeatScratch-Flutter). I’ve let it sit unmaintained (because it’s been “good enough” at its job) for a couple of years, through the addition of null safety to Dart and numerous Flutter changes (though I have to say, its API stability over this time is pretty impressive!). I’ve also GPLed the code in that time and the new version will also be under that license. Once I’ve got at least the iOS and web release pipelines working again, I plan to replace its Reddit integration/sharing features with an implementation based on https://jonline.io (https://github.com/JonLatane/jonline), the AGPL, Rust/gRPC-based social network I’ve built in the intervening time. I’m also planning on adding more detailed (left to right audio) panning and other output controls, oriented tow

Various ways in various companies, but in my last few companies pretty much always “CI runs tests and builds/uploads a Docker image, CD deploys it onto a K8s cluster somewhere.” In the case of my major current personal project, I do it with a GitHub Actions workflow: https://github.com/JonLatane/jonline/blob/main/.github/workf... A deploy looks like this: https://github.com/JonLatane/jonline/actions/runs/1346474905... Here, I do a canary deploy to a dev server (jonline.io), then cut a GitHub release and deploy to production servers (bullcity.social, oakcity.social). (All really live on the same single-box dinky K8s cluster.)