muslrust VS himalaya

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.

Before you going deeper, take a look at himalaya if it fit to your needs.

https://github.com/soywod/himalaya this one also is a thing, has a vim plugin too

Take a look at Himalaya: https://github.com/soywod/himalaya

You can use himalaya for that

We live in a time of a Renaissance of terminal tools. I recently discovered Himalaya[1], a command line tool for email, and I really like it. I'm also interested in exploring a new tool for calendar called qcal[2]. I'm kicking around writing a chat client for GroupMe for the terminal right now. That way I could finally ditch pidgin.

Like the OP, I spend all day in tmux these days, which is in many ways the most superior UI[3]. As a bonus, CLI tools are often cross-platform and very easy to write.

1: https://github.com/soywod/himalaya