I’ve been trying to move some of the Soniq application logic into WebAssembly using wasm-pack. I’m not sure whether it makes total sense at the moment, but I figure, the best way to find out is to do it and analyse the results.
I have been building an invoicing section which will take a set of lessons and create the corresponding invoices. It’s a relatively clean operation, I can feed in a load of lessons and contacts and it should respond with a list of invoices and invoice lines.
I have recently added wasm-pack builds into my Soniq project but found that it is a nightmare trying to get rustup and cargo installed in the Vercel build alongside my yarn monorepo.
I have been planning to migrate my deployments to pure Github actions and this was the push to strap myself in and get my hands dirty.
So here is part 1 in a series where I will explain the steps I have taken to get my monorepo building and deploying efficiently with Github Actions using Turborepo and a few, key, architecture decisions.
One of the best decisions I made in 2020 was to open my calendar to everyone. People book appointments to chat about open-source projects, content creation, and business ideas.
This reminded me that I have wanted to do the same thing for a while. So I have opened up my calendar as well, and booked a chat on his.