So you need to read a whole book to deploy Elixir, people say Elixir is easy and straightforward but I think they are downplaying the amount of overhead BEAM/OTP/deploying brings to the table.
Looking at the contents of the book it looks like it goes into depth on how "releases" work, and gives guides to using a bunch of popular platforms like heroku, digital ocean, etc. It's looks like a conveniant collection of recipes for different hosting options.
This isn't even remotely true. When I learned Elixir in 2016, I was able to deploy using the exact same setup as I'd used previously for Node and then Rails. This was a Phoenix app, run using mix.
Then the next day, I learned how to compile and run an Erlang release. This made deployment simpler than anything else I'd worked with previously, though not quite as easy as I've since experienced that compile down to a native binary with no external requirements at all.
Now, Phoenix even has a flag to build a docker container with a single mix command. It's not quite as easy to deploy as Go or Rust, but it's truly hard to imagine an interpreted language getting much easier.
I disagree with the claim that the book's existence is evidence of a deficiency in the ecosystem. That's nothing against the book itself! On the contrary, creating more resources like this is a win for everyone.