Welcome to Livebook discussions!

[josevalim]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we build together 💪.

To get started, comment below with an introduction of yourself and share with us the cool things you are building with Livebook!

[BrooklinJazz]

Hello! Thank you for making this space Jose, I'm really excited about it.

I'm Brooklin Myers. I'm building DockYard Academy in Livebook.
I also host the Elixir Newbie podcast.

There are some fun projects that have come out of the academy.

• A slide show widget with Kino
• A livebook testing DSL
• A validated form widget

Also if you haven't already seen it @jonatanklosko's Kino Lab project has a Youtube widget that lets you add videos to Livebook. It's been incredibly important to academy content 🙏

Feel free to reach out to me any time if you want to chat about Livebook. I'm happy to share what I've learned!

[kaiserdan]

Hi everyone!

I'm a huge fan of livebook too and use it with with EEx as a BI tool to generate generic SQL code collaboratively, and with a custom Kino widget to visualise the queries as charts with JS libraries. Super excited to see where you'll take it - it's really wonderful tech to work with.

[josevalim]

Welcome @kaiserdan! I think you are going to love the features coming in Livebook v0.6, as they closely relate to your use case!

[markomitranic]

Hey Jose, I'm a big fan of all your work. Those Twitch streams were insanely valuable 😃

I work at a medical device company, and we often use Livebook as a replacement for internal "admin panels". They enable us to keep "recipes" for common DevOps or Engineering operations, with which we connect to the remote BEAM Node and execute them in-place.

Yknow, stuff like manually meddling with database information and migrations, complex deletions, application of hotfixes, production debugging when we didn't cover a process well enough logging-wise, getting custom-made reports, live-tailing actions, managing kubernetes deployments and namespaces etc.

Its not intended to be a permanent thing. It allows us to keep track of snippet changes that we would usually use iex for - while requiring FAR FAR less time than making an "admin panel". Over time, we see which worklows get repeat often, and document or automate them in a better way.

[Adzz]

That's great, I am writing a blog post where I suggested this exact use case! Interesting to see you are doing it.

[Adzz]

Hi everyone, 👋

I work at Duffel

Big fan of livebook so thanks to Jonatan, Jose and the team!! ❤️

I have introduced them at work for:

1. Onboarding (both for learning Elixir and our own tech stack)
2. Scoping out APIs - we write a lot of integrations so we use Livebook to explore and document them before implementation.
3. As the default REPL.

To aid with the above I am working on a secrets library that would allow you to fetch secrets from an external store (like Google Secret Manager) and read them securely into your livebook.

I have also written livebook_helpers a library that will generate a livebook from your module documentation. This is great because it means you can have one source of truth for docs and generate the livebook when you publish to hex for example... Or you can easily bootstrap the creation of a livebook for an existing library without having to repeat yourself. I've been experimenting with creating livebooks for all the Elixir modules for example.

[rugyoga]

I work at Lob doing Address Verification.
Almost all of our AV functionality is written in Elixir.
I introduced the rest of the team to Livebooks with several demo of how to hook it into Dora (our AV repo).
On a personal side, I race cars for a hobby and am looking at using Livebooks and Nerves to build
novel equipment for instrumenting my vehicles.
I've also started writing a chess program.
Live books is definitely a game changer for my use cases.
Cheers,
Guy
p.s. If I have bugs to report, where's the appropriate venue?

[leaked]

You can report from this section
https://github.com/livebook-dev/livebook/issues
https://github.com/nerves-project/nerves/issues

[jonatanklosko]

There's also https://github.com/livebook-dev/nerves_livebook depending on what the bug is. If you're unsure you can also open a discussion thread in the Q&A Discussions section :)

[rugyoga]

#1131