The lua shell does not give full access to the elixir runtime. It is a sandbox. You have the ability to add lua functions that can execute elixir code. That way the access to the system is limited/controlled. lua provides a powerfull way to automate tasks. And a shell allows to do that interactively.

I subscribe to everything you said here, chilli con carne included!
And thank you for this one!

That I understood

A shell running lua would provide a really powerful way to interact with your application.

That’s something I probably would have avoided in general. Yeesh is exposed to the client. Giving it a full remote access to the server application sounds like a perilous idea. If I were after that, I’d probably start with an ability to execute an arbitrary elixir code.

Instead, Yeesh allows whitelisted mix tasks, including interactive ones. Wrapping the aforementioned library into an interactive mix tasks should not be difficult, but at the moment it is out of scope of my actual needs.

Feel free to create an issue in github though.