How do I configure a secret file contain secret keys to digital ocean hosted app?

  • Posted on February 9, 2015
  • gurumeAsked by gurume

Hi guys, my ROR app uses Stripe to handle payment transactions. When our app was hosted using Heroku, we had the Stripe api keys inside a secret application.yml file. But now that we are hosted under DOcean, am I right in thinking that we need to configure this application.yml file to digital ocean? If so, please may I ask for some help out points please? I’m really stuck and some pointers would be much appreciated thank you!


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

A lot of this depends on how you deploy your application. A general best practice followed by many developers is to use environmental variables to hold secret tokens. Rails 4.1 introduced the config/secrets.yml file in order to standardize how to access thing like this in applications.

If you used the environmental variable STRIPE_TOKEN to hold your token, you can source it in your config/secrets.yml like:

  stripe_token: <%= ENV["STRIPE_TOKEN"] %>

You can now access it using Rails.application.secrets.stripe_token

dotenv is a useful gem that loads the contents of a .env file into ENV