7 comments

[ 1.7 ms ] story [ 27.0 ms ] thread
A few thoughts here:

1. LiveBook is awesome and just continues to get better.

2. The Elixir core team is pumping out some fascinating stuff, taking inspiration from other languages and ecosystems and improving upon the products.

3. The author of this post is Mark Ericksen, co-host of the Thinking Elixir podcast, and I highly recommend it for anyone looking for an Elixir podcast! It's my favorite.

4. This is a really cool article, I hadn't thought of using LiveBook as an actual BI tool but I might actually try it out. I've thought about using it as documentation, and in tandem with something like this might get me over the hump.

Yeah! Big thanks to Mark and the Fly team for pushing Elixir hard on their platform.

This is a fantastic article and as you said, a novel use case of Livebook I hadn't thought of before.

Does anyone know - is it possible to restrict yourself to read-only operations? It's fairly easy to accidentally break something in production environment...
What do you mean read-only? You could pull data from a read-only data source.
I mean something that prevents me to accidentally update data in a database or call an external service. Preferably based on my credentials.
Is Livebook git-compatible in a sane way, unlike Jupyter?
I'm not familiar with how Jupyter works, but I would guess so. Livebook "notepads" are just text files.