Earlier quoted context omitted.
thanks for the detailed answer of the differences. The interactive (I assume using CRDT's) is a good feature, jupyter server does not have this and is at a time a bit of a hassle. Also deploying it directly as an app is pretty sweet.
Livebook actually uses state reducers as described here[1]. Except for cell content. There it uses Operational Transformation. The source code[2] is really instructional and easy to understand. I highly recommend to look into it :) [1] https://github.com/jonatanklosko/notebooks/blob/main/article... [2] https://github.com/livebook-dev/livebook/blob/main/lib/liveb...
Elixir Livebook is a secret weapon for documentation
61–70 of 72 posts
Re: Elixir Livebook is a secret weapon for documentation
#62While I'm glad the idea of tying documentation to tests is catching on, I think markdown documentation -> create tests is the wrong way around. I built this tool to let people generate evergreen markdown documentation from annotated type-safe YAML integration tests: https://github.com/hitchdev/hitchstory
This is incredible work. To anyone curious, I highly recommend: - https://hitchdev.com/hitchstory/approach/ - https://hitchdev.com/hitchstory/why-not/ From the overall RDD/BDD type home page: - https://hitchdev.com/hitchstory/ The entire product site is a thing of richly informative beauty. --- My only question was whether the generated 'docs' snippets would add value over just reading the story in your DASL. Any mar…
Re: Elixir Livebook is a secret weapon for documentation
#63Earlier quoted context omitted.
Sure, here's a simple demonstration of what livebook can do that docusaurus cannot, at least without maintainer expertise ;) Imagine the following. we click a play button to start an elixir runtime based on that metadata code block with this component, we then issue commands to inspect state, manage elixir "processes" in the runtime, etc
> we click a play button to start an elixir runtime based on that metadata code block Can you show a concrete example? IE a real production url running this? What is "metadata"? In Docusaurus you can have a live playground evaluating on your browser, or you can embed any embeddable playground if it requires a server integration. > with this component, we then issue commands to inspect state, manage elixir "processes"…
Re: Elixir Livebook is a secret weapon for documentation
#64Earlier quoted context omitted.
Sure, here's a simple demonstration of what livebook can do that docusaurus cannot, at least without maintainer expertise ;) Imagine the following. we click a play button to start an elixir runtime based on that metadata code block with this component, we then issue commands to inspect state, manage elixir "processes" in the runtime, etc
> we click a play button to start an elixir runtime based on that metadata code block Can you show a concrete example? IE a real production url running this? What is "metadata"? In Docusaurus you can have a live playground evaluating on your browser, or you can embed any embeddable playground if it requires a server integration. > with this component, we then issue commands to inspect state, manage elixir "processes"…
The code blocks need to be run in sequence, from top-down, as one builds on the next. The "metadata" at the very top often describes the project and its dependencies.
Re: Elixir Livebook is a secret weapon for documentation
#65Today, in a very round-about way, one could use a livebook as if it were a blog post: download-install Livebook on your machive, download the blog post livemd file, run it locally. Here's an example. Note in the first paragraph a link to the post as a livemd file: https://genericjam.com/blog/image-processing If you go through the steps, you'll notice that the livemd isn't stylized as a blog post. This is where the ne…
Is there a way to render the livebook as read only until they try a change? I tried to open the link and it failed. I could download it and run it but I just want to see it as you intended.
Re: Elixir Livebook is a secret weapon for documentation
#66I would suggest to anyone to download Livebook and test it out, even if you don't know Elixir or Erlang. You can do so much with it. I even use it for things outside of programming due to it being pretty much a markdown notebook that you can run code inside of. It's one of my favorite tools.
For linux the easiest way to download livebook is with docker [1] or maybe with fly.io [2]. Installing it directly is a bit complicated if you are not familiar with it. I wish linux also had Desktop app like mac. [1]: https://github.com/livebook-dev/livebook#docker [2]: https://fly.io/launch/livebook
Re: Elixir Livebook is a secret weapon for documentation
#67Earlier quoted context omitted.
For linux the easiest way to download livebook is with docker [1] or maybe with fly.io [2]. Installing it directly is a bit complicated if you are not familiar with it. I wish linux also had Desktop app like mac. [1]: https://github.com/livebook-dev/livebook#docker [2]: https://fly.io/launch/livebook
I managed to install it with devbox (nix under the hood), works very well !
Re: Elixir Livebook is a secret weapon for documentation
#68This concept sounds quite a bit like the usage of .mdx files in OCaml. Those are markdown files which can load and execute OCaml code in them. They are useful for unit testing code like libraries, providing usage examples for end-users (as well as the text format markdown usually supports) and testing it at the same time. Definitely a great idea for documentation, and one which I should use more of. https://github.co…
Apart from running code inside a "markdown" file, livebook can do much more. You have Smart cells to show charts, run sql queries against a db, run Neural Network tasks such as Image-To-Text generation using Bumblebee[1], etc. It is collaborative as well. [1] https://github.com/elixir-nx/bumblebee
Wow!
Re: Elixir Livebook is a secret weapon for documentation
#69One simple thing I need thats stopping me from jumping into Livebook fully: Salesforce API integration. Right now, I can't manage to make the auth work there (since oAuth needs some http redirect dance). Connecting to some proper SQL database is a breeze, but if I cannot access some silo'ed data that is absilute critical, its not that useful after all :-/
Please open up a discussion on Livebook repo? We would love to understand more what is missing here. :)
But on the topic: I think its a simple problem ultimately, the SF Api (https://developer.salesforce.com/docs/atlas.en-us.api_rest.m...) needs OAuth, which needs a redirect at some point, where I have no idea how to capture it from a livebook instance (easy in a phx app).
This is a reference lib in JS ( https://jsforce.github.io/ ) and there seems to be no maintained alternative on hex.pm unfortunately. So, from scratch it seems, somehow.
Additional insight: many big companies do use salesforce, and its internal tooling to produce reports/insights is rather limited, but there is a SQL-like language to do complicated stuff, but there is no way to execute a handwritten query in SF itself, except via API calls from outside. This... would be a perfect fit fro livebook! query SF + other databases to generate a report ad-hoc thats not easily possible right now without adding some heavyweight data warehouse connection!
Re: Elixir Livebook is a secret weapon for documentation
#70Earlier quoted context omitted.
Please open up a discussion on Livebook repo? We would love to understand more what is missing here. :)
I slightly complain a single time for the last few years, and jose directly chimes in with kind words immediately. You rock, honestly! But on the topic: I think its a simple problem ultimately, the SF Api ( https://developer.salesforce.com/docs/atlas.en-us.api_rest.m... ) needs OAuth, which needs a redirect at some point, where I have no idea how to capture it from a livebook instance (easy in a phx app). This is a r…
If this is something you would like to work on, please reach out, I think it could open up interesting possibilities!