title: What's the point of secrets.yml if I still have to load variables from environment?
body: <p>I decided to use secrets.yml file as a way for me to easily transferring my variables to my app's production server. Once i open up the file, this is what I notice:</p>
  
  <pre><code>development:
    secret_key_base: 61a3857f1ddc140836......
  
  test:
    secret_key_base: 6041df556cf0feb5e.....
  
  # Do not keep production secrets in the repository,
  # instead read values from the environment.
  production:
    secret_key_base: &lt;%= ENV["SECRET_KEY_BASE"] %&gt;
  </code></pre>
  
  <p>As you can see, for the production part, it says <strong>"Do not keep production secrets in the repository, instead read values from the environment"</strong></p>
  
  <p>I don't know about other people, but it's so obvious to me that if i do this, it will completely defeats the purpose of the secrets.yml itself. I want to use secrets.yml myself so that I do not have to set the environment variables one by one via the terminal on the production server anymore, but then if I still need to do this even if I am using the secrets.yml now, then whats the point?</p>
  
  <p>Setting up and transferring variables from development to production process have been bugging me for a really long time. I have been trying to look everywhere but no one seems to be really clear about the process from start to finish. So, sorry if this seems like a stupid question.</p>