In this post I show you the approach I've been using for a while to simplify some aspects of the packaging of my apps. Through it all I will try to convince you that waiting a long ass time for project to build is a sign of greatness (somehow)

This is a showcase of the app I've been working on and off for a while now, which recently got a major update and public release. A http4s and smithy4s full stack application which provides a web interface to my Scala Native bindings generator

We stop at nothing to avoid manual work in tweaking our scalafmt config to produce the least amount of changes in the existing files

In this installment, we introduce NGINX Unit (and SNUnit), build out the foundations of our API, and set up a deployment to Fly.io

In part two, we will setup bindings to Postgres and OpenSSL, and write a data access library to make working with Postgres easier

We embark on an adventure of infinite struggle, trying to build an opinionated (=bad) Twitter clone using nothing but Scala Native and C libraries, Scala.js for frontend, Postgres for database, and Fly.io for cloud deployment

How to build, deploy, and develop an app using Cloudflare functions with Scala.js, choosing most difficult routes on every turn