bc3-api VS muslrust

Remote work is an established term these days, but back in the days i.e. prior to COVID or a few more years back, this term was quite alien in the developer community. Even though there were organizations like Basecamp which were working remotely for more than 20 years, the developer ecosystem was not built around the concept of working remotely or to put it in simple words, separately from your colleagues. Just like other industries, it was sort of mandatory to share the physical space with your peers in-order to achieve some work. So if you‘ve asked HR in 2014 about remote work, they would definitely have raised an eyebrow.

It's interesting, I've sampled basecamp.com and the number was 35 too, very similar variables, taking into consideration Basecamp is Older than Hey and heavily flex-box oriented.

David Heinemeier Hansson, also known as DHH, may not be a familiar name to you, but it's highly likely that you have come across either the product or the framework he created: Basecamp and Ruby on Rails.

(Basecamp: Project management software, online collaboration) Trusted by millions, Basecamp puts everything you need to get work done in one place. It's the calm, organized way to manage projects, work with clients, ...

I think you want to look at Basecamp and even Slack may work for you.

Some of you may be familiar with the creators of Basecamp. They often seem to be a small but powerful group that influences trends in the software industry.

You are looking for a Project Management software like BaseCamp or Slack.

That's isn't true, one can make fully independent static binary in rust

The winning combo that I found works great is a multistage build, using clux/muslrust to build the dependencies + the binary itself, then using a scratch image as the final stage. Depending on the complexity, the statically linked images I use range from ~9MB to ~22MB. The 9MB image was ported from an existing container that was dynamically linked, and if I remember right, the image was in the ~70-80MB range using debian:buster-slim as the final stage.

muslrust: seems to be active last commit on Oct 2, 2021. But what is the difference compared to the one above?

Oh, I remember that I use https://github.com/clux/muslrust and is there what the bug is triggered. Weirdly, running it locally not show it.

After a lot of searching I came across a Docker image which provides a clean environment for building Rust linked against musl libc. It includes curl, pq, sqlite3, and zlib, but the main one I needed was OpenSSL. This container image solved my problem and I can run using Docker locally as well as in the GitHub Action build workflow.