In a support discussion titled ‘How to setup heroku ENV variable for sso secret?’, railsnoob asks how to securely store an SSO secret in a Rails app using Heroku environment variables instead of hardcoding it. They initially share code with a hardcoded secret and inquire if using heroku config:set DISCOURSE_SECRET=ilovetomcruise followed by ENV['DISCOURSE_SECRET'] would work. pfaffman initially misunderstands the question, assuming the user is configuring Discourse itself via its web interface and recommends following the official Discourse cloud install guide. After clarification from railsnoob, pfaffman admits they’re not familiar with SSO from a separate Rails app. Finally, alxpck confirms that Heroku’s config vars work as railsnoob suggested, directing them to Heroku’s official docs on config vars for more details. The core takeaway is: yes, use heroku config:set DISCOURSE_SECRET=ilovetomcruise to set the secret, then reference it via ENV['DISCOURSE_SECRET'] in code.
I thought that stuff goes into my Rails app? I installed with those instructions awhile ago. If everything is on the digital ocean server how will it communicate with my app?
Oh. Do you mean that you have written a Rails app that you would like to SSO authenticate against? I didn’t understand that at all from your post. Sorry. I’m no help help here.