dmitriid
Is there a reason why Livebook secrets are automatically prepended with LB?
I spent probably 15 minutes trying to figure this out until I ran into What's new in Livebook 0.7 - Livebook.dev - The Livebook Blog and actually read through it because it’s somewhat buried at the end after a video.
You add a secret, API_SECRET_KEY, but to actually fetch it, you need to fetch LB_API_SECRET_KEY. Is there a reason for this?
Marked As Solved
dmitriid
Added an issue: [Usability] Help text/popup/description that env variables are prefixed with LB_ · Issue #1827 · livebook-dev/livebook · GitHub
And while writing it discovered that there’s help text, but I never saw it ![]()
Also Liked
hugobarauna
I think one of the reasons is that a defined namespace allows Livebook to detect “environment variables” that Livebook is supposed to manage and give them special treatment.
Here’s a quick GIF video showing that difference:
BartOtten
—skip—
I see no reason other than well intended namespacing…with confusion as result.
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










