Now if I click this you're going to see that I have all these weird characters here. Now you may notice we don't have a secrets file anymore. In years past, what you would do is you'd have the config directory here and then inside of here you'd have the secrets. I'm going to first show you in the file system how it's different. If I open up the application and I'm using vim here, but it's perfectly fine for you to use Sublime Text or anything like that. That's just going to create the database, and then create a schema file for us. I'm now going to change into this application cd CredientialsApp, and now I'm going to quickly create the database and migrate it so I can say rails db:creates & rails db:migrate. The reason for that is because there is a little trick that you need to do in order to get this working on Heroku, and I want to show that to you as well here.
Then I'm also going to use the postgresq database. I'm going to say: rails new CredentialsApp -T -database=postgresq. So I'm going to build out very quickly here in New applications. In this guide, I'm going to walk through how you are able to do that. Now in versions 5.2 and above, you can actually store those inside of the application, and access them which is really nice and handy.
This would be anything from say AWS credentials for connecting to Amazon Web Services, to your secret_key base, to Twitter or anything like that. m or Figaro, in order to protect your credentials so that no other users could see them, but you could still use them in your application.
In any older version of rails, you would use a tool such as.
0 kommentar(er)
