spagyther
Where should a dev store their LiveBooks in a Phoenix app?
This is a soft question, so please bare with me.
During the development of virtually every Phoenix app, there comes a moment where I want to try stuff out, so I open a LiveBook and connect it to a running instance of said application. In some cases, I use multiple LiveBooks to follow SoC.
Fact is, I’d like to keep those LiveBooks I use during development somewhere in the app’s directory. However, I never know where exactly to put them in a way that is conformant to OTP app folder structure. Intuitively, I believe they should go somewhere in priv, but are computing notebooks of any kind executables? Are they libraries? I think neither. Here I am referring to the official Erlang docs:
The priv directory holds assets that the application needs during runtime. Executables should reside in
priv/binand dynamically-linked libraries should reside inpriv/lib. Other assets are free to reside within the priv directory but it is recommended they do so in a structured manner.
So it would fall in the “other assets” category, so it could look something like priv/livebooks. Could this make sense? What do you think?
Most Liked
hugobarauna
What I’ve been seeing is people just creating a /notebooks directory and putting their Livebook notebooks there.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









