dropthejase ditches containers for a lighter backend
The Louis fork swaps a Docker-based deployment for a simpler bundle-and-ship setup, and cleans the kitchen on the way out.
dropthejase has reversed an earlier architectural bet. The backend that powers Louis used to ship as a container - a heavier packaging format that needs Docker installed on every developer's machine and a hand-written deploy script to push it to AWS. The team has now moved to a plain zipped bundle, letting AWS's own infrastructure-as-code tools handle the assembly. The bespoke deploy script is gone, replaced by a single standard command.
Along the way, the team trimmed unused document-handling libraries, upgraded the underlying runtime to a current version, and turned on the settings that make production crashes actually debuggable rather than appearing as a wall of mangled code. The database engine was also bumped to a newer Postgres release.
It's the kind of housekeeping that doesn't change what users see but materially changes how fast the team can ship and diagnose problems.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?