JasterV
Hello there ![]()
I am using the vintage net wifi package on my nerves project.
I don’t want to source my WIFI credentials to git but unfortunately the WIFI is configured at compile time and I need to pass the credentials in my target.exs file.
I was wondering if someone figured out a way to read the wifi credentials from a configuration file at compile time that is not sourced to git.
I’ve tried to read from environment variables but I have problems trying to load those environment variables into my system because of the following:
I’ve thought on having an environment variable WIFI_SSID_LIST=ssid1,ssid2,ssid3
but if the SSID contains &, the export $(cat .env | xargs) command will fail:
export: not valid in this context: &
So then I started thinking on having a separate file and reading it using File.read on the target.exs but I am not sure about it.
Is there someone that has tried something else?
Trending in Questions
Other Trending 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
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










Showing Posts 1 to 4- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
ConnorRigby
target.exsis a Elixir script, so you can populate that data from anywhere. I sometimes do things like thisYou can extend this to have a list if you want as well.
you don’t have to set them at compile-time. you can do this:
And then configure it at runtime with
Hermanverschooten
I don’t know what OS you are running on, but have you tried to
sourcethe.envfile instead ofcattting it?source .envJasterV
I am running Mac OS,
source .envonly works if the .env file declares the variables with theexportkeyword at the beginningso I had it like
now I’ve changed it to:
and now it works
I didn’t want to use the export keyword since most libraries like
dotenvdon’t require it but I guess its fineJasterV
Thanks so much
Configuring it at runtime looks like a good solution for my use case