I’m configuring the Scout addon for my rails application using the
config/scout_apm.yml file but the key isn’t being picked up so my application isn’t connecting to Scout.
rake scout:doctor rails command through the Render shell shows that the key is being set to
nil by an environment variable (see screenshot)
I can also find the
SCOUT_KEY in the rails env variables set to
nil with this
ENV.keys['SCOUNT_KEY'] #=> nil.
SCOUT_KEY env variable is overwriting yaml config. My app doesn’t have a
SCOUT_KEY env in it’s settings.
SCOUT_KEY is set somewhere by Render after installing a global addon?
SCOUT_KEY is being set to
nil in another rails app running on Render where the Scout gem not installed.
nil value by setting
SCOUT_KEY in my app’s env variables.
SCOUT_KEY shouldn’t exist in my app’s env variables.
I would like all my credentials to live in the rails
config/credentials.yml.enc file so the app if fast & easy to port to other environments and providers with minimal ENVs.
Ideally, even if the addon correctly populates the
SCOUT_KEY, I would like the choice to remove it so the yaml file credentials are used.