Rails and the hidden credentials

Moving away from ENV

One of the challenges that cropped up during this projects was that we had to use Omniauth to allow a user to sign in via Facebook, Google, or the like. Problem I had was that even after following online tutorials it still wasn't functioning as it should.  Through trial and error I discovered that it had something to do with using the ENV variable.
After doing my homework there was a lot of suggestions to use the new Rails Credentials setup.  This was a bit more difficult as adding credentials to the credentials.yml.enc file isn't as simple as just pasting them in.
First you have to get into your credentials.yml.enc file.  If you just open it you'll notice it has a single line of hexadecimal code. Do not edit this directly.

To edit this file you'l need to enter the follow command in your terminal:
EDITOR="atom --wait" rails credentials:edit 

Replace "atom" with your own editor.  This will bring up the file you need to edit.  The syntax to setting up your credentials is:

name_of_group:
id:
secret:
  For example:

aws:
access_key_id: YOURACCESSKEY
secret_access_key: YOURSECRETACCESSKEY
 You can put as many different credentials as you want in that file, just separate them into groups.
Once that is done, save the file and close it.  If you look in your terminal you should see "Encrypted and saved" but you can also confirm this by running:
rails credentials:show
Now you'll need to insert this into your code.  Where ever it is you need it you'll insert Rails.application.credentials.dig()

Using the example above it would look like this:
amazon: service: S3 access_key_id: <%= Rails.application.credentials.dig(:aws, :access_key_id) %> secret_access_key: <%= Rails.application.credentials.dig(:aws, :secret_access_key) %> region: us-east-2 bucket: <%= Rails.application.credentials.dig(:aws, :bucket) %>

Comments

Post a Comment

Popular posts from this blog

Introducing Dir

Image
While learning JavaScript I learned about console.log() . In the course of using JS I used the quit often.  It's a great debugging tool for doing thing like seeing exactly what a function or variable is returning or even as a build tool to see what a fetch request returns.  I've even used it to see what order my code runs in when using asynchronous code. Recently I learned about a different version of this, console.dir() . Here is what the official docs have to say about it: The  Console  method  dir()  displays an interactive list of the properties of the specified JavaScript object.  The output is presented as a hierarchical listing with disclosure triangles that let you see the contents of child objects. You can read more from the official docs  here .  This is something I hadn't seen before through my entire time in school nor in any of the tutorials I found online.  I'm sure there is some reason I am unaware of that no one s...
Read more

Flatiron Final Feelings

Image
My feeling about my time at Flatiron Well I'm at the end. Six months ago I took a giant leap and went back to school.  No small feat for someone nearing 40 with bills to pay, but I did it.  There where lots of ups and downs.  I met a lot of great people along the way and learned more than I could ever think I could. The Good: The people, the help, the lessons.  My favorite section was on Rails.  I aced and soared through that.  I got really good at everything to do with Rails to where I was helping other students daily. Which leads me to the bad..... The Bad: While JS isn't that hard for me now at the time I was riding this kind of confidence high from Ruby and Rails.  Then I hit Javascript. I wasn't catching on the way I was with Rails.  I even had to take a step back and go over everything again.  It put me behind.  My confidence was shot. There where tears. At the time I was devastated.   I though I...
Read more

Teaching to Learn

    Recently I have been helping new comers to my alma mater learn to code.  This is my way of giving back and helping to pull others up along with me.  Along the way I have discovered something about teaching: I learn more from teaching than I do from just going to classes or watching tutorial videos.     Teaching forces you to keep up with the newest trends like syntax changes and different ways to write code you already learned.  It also enforces good debugging techniques and thinking out loud, forming your thoughts into questions.  It keeps the basics fresh while still being able to flex all the fancy code and techniques you learned along the way.     It also forces you to think outside your own box.  For example when I was in school we had to build a project using only Ruby on Rails for frontend and backend.  One of the requirements is to setup 3rd party authentication through Oauth.  When I build mine and for a few o...
Read more