# Stubbing Rails Secrets into Build

**URL:** <https://discuss.circleci.com/t/stubbing-rails-secrets-into-build/26004>\
**Category:** Build Environment\
**Tags:** rails, ruby\
**Created:** [October 24, 2018, 9:29pm UTC](https://discuss.circleci.com/t/stubbing-rails-secrets-into-build/26004 "2018-10-24T21:29:37Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![jnguyen1990](https://avatars.discourse-cdn.com/v4/letter/j/8c91f0/32.png) [@jnguyen1990](https://discuss.circleci.com/u/jnguyen1990)\
**Post date:** [October 26, 2018, 6:56pm UTC](https://discuss.circleci.com/t/stubbing-rails-secrets-into-build/26004/9 "2018-10-26T18:56:19Z")

</div>

Oh thats strange. I saw it here [How can I set secrets.yml for test environment for CircleCI?](https://discuss.circleci.com/t/how-can-i-set-secrets-yml-for-test-environment-for-circleci/2304)

Essentially I just need to load a fake `secrets.yml` file or just replace the `mailchimp_api_key` secrets key that is called.

Is there a reason why I can’t just use Settings -\> Environment Variables?

---

_[View the full topic](https://discuss.circleci.com/t/stubbing-rails-secrets-into-build/26004)._