This is not good advice. 

If you actually put `SecureRandom.hex(64)` into a file executed at boot time, like an initializer, you'll get a different key each boot. 

Which among other things, means if you are running a cluster of multiple processes, each will have a different key, and a url generated by one of them will be rejected if when refworks calls back it ends up connected to a different one. Other problems in this class too. 

That's why I recommended running `rake secret` -- you need to hard-code the secret key, same as Rails app secret key is, you can't have it dynamically generated on each boot. 

Our templates calling `SecureRandom.hex` at _app install time_ work fine, but putting `SEcureRandom.hex` in an initializer will not. We need to recommend `rake secret` instead, and then putting the results in your initializer, no?