To save you some time it should just be a case of: 1. installing direnv (brew install direnv) 2. move the .env file contents to the .envrc in the project root (with some minor formatting tweaks) 3. running `direnv allow` in the project root
Unless you're using envrc in production (which I wouldn't, and can't remember ever seeing) then that should be everything you need to change. In production there would be no changes if you're setting env vars in the normal way (eg. "settings" in Heroku, systemd config etc.). If you /are/ using envrc in production then you might find the config to be better moved to those "normal" ways of setting the env, initialisers or the credentials store. Will. > On 27 Jan 2024, at 09:41, 'Rob Whittaker' via North West Ruby User Group > (NWRUG) <nwrug-members@googlegroups.com> wrote: > > It may be the Baader-Meinhof effect, but I've seen more mentions of direnv > over the last day than I have ever before. I've added a card to my backlog to > investigate swapping out dotenv. -- You received this message because you are subscribed to the Google Groups "North West Ruby User Group (NWRUG)" group. To unsubscribe from this group and stop receiving emails from it, send an email to nwrug-members+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/nwrug-members/FD10D797-72DE-4D20-80F8-F04E5D184C61%40willj.net.
