totally fair point! the medium/long-term roadmap is to layer in a BBS-esque community, so identity is required. more on this later! regardless, might be nice to have an unauthenticated / "Skip sign in" flow for the folks who just want to use the tool.
I built a TUI sampler which cherry-picks my favourite features from modern & vintage hardware samplers, DAWs, plugins, outboard FX gear, and DJ equipment.
If you know what an AKAI MPC Live, MPC 3000, SP404, SP1200, BOSS RC-202, Alesis 3630, Serato Sample, S950 filters, and stem separation does, then you'll love seeing these "greatest hits" up in a terminal interface.
Last year while on vacation in Costa Rica, I started scratching my own itch for locating and organizing samples, which quickly evolved into adding more and more features while keeping it tactile and immediate. It was too fun to stop so I kept going. After a few days I was happily making beats in it, and since then it's only gotten better.
It's live and totally free to use, and works in macos & Linux (Windows soon). I'm about to launch v1.0 now, just working with folks in the community to round out the Factory Kits a little more for users new to beatmaking.
Turns out, making beats with no mouse and a terminal interface strikes the perfect balance of hardware feel and software power, and I'm loving the result. Been sharing it with folks in my beatmaking sphere and have plans to continue expanding its reach through more collaborations, contests, and in-person events.
Hope it brings you as much joy as it does to me :)
Awesome. Do docker image layers persist across build runs? Github, BuildJet, etc. use ephemeral runners, so subsequent runs have to re-pull everything from scratch, which is where most of my actions' time is spent now. If you're able to persist these across runs, that'd be a reason to switch alone.
Congrats on the launch! I've spent some time recently with great success speeding up CI for my teams via alternate actions runners, and the increase in efficiency that comes with dramatic reductions in build times is worth it. When the cost is the same (or less), it's an absolute no-brainer.
How do you differentiate from BuildJet, which takes a similar approach?
Peggy | Senior Back End Developer - Ruby/Rails | Full-Time | REMOTE: US, Canada, Global*
Peggy partners with galleries and artists to make living with and investing in art accessible to all. Finally you can buy incredible art at a price you can afford, and can later sell to fellow collectors if your tastes change or you seek to rebalance your art investments. Core to our values, Peggy does good by the artists themselves, who can finally earn artist royalties for all future secondary sales as well - something they miss out on today. This is all made possible using sophisticated and proprietary AI and ML which keeps buyers and sellers protected without the need for the antiquated and opaque Auction House model.
As a key member of the back end team, you will be responsible for providing an elegant and well-documented GraphQL API as an entry-point into Peggy’s content, data, and business logic, which is crafted in Ruby, Rails and Postgres. You will be supported by a DevOps infrastructure, which leverages AWS, Terraform, CI/CD, CloudWatch, Auth0, Sentry, and other developer-friendly tools and systems.
Peggy is a remote-first company. We are building the company this way so we can curate a team with the best talent from anywhere in the world, and to create flexibility for team members. Team members (incl. ex-Shopify, Uber, Ada) currently/recently working from: Toronto, Vancouver, CDMX, Brazil, Argentina, London, India, Sweden, Lisbon, Madrid, NYC.