# Trouble adding vault-rails gem to a plugin

**URL:** <https://meta.discourse.org/t/trouble-adding-vault-rails-gem-to-a-plugin/173291>\
**Category:** Development\
**Created:** [December 14, 2020, 8:53pm UTC](https://meta.discourse.org/t/trouble-adding-vault-rails-gem-to-a-plugin/173291 "2020-12-14T20:53:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [December 14, 2020, 9:14pm UTC](https://meta.discourse.org/t/trouble-adding-vault-rails-gem-to-a-plugin/173291/3 "2020-12-14T21:14:36Z")

</div>

Oh. It never would have occurred to me that `rails` wasn’t loaded.

**all the dependency tree**! I see.

It does seem like a lot of stuff.

I’ll be storing stuff like a digital ocean api key and an ssh key in the database. Do you know, offhand, another simple way to do that safely? I suppose that I could just shell out and run `vault` or something like it with an `exec`. It won’t be happening that often.

---

_[View the full topic](https://meta.discourse.org/t/trouble-adding-vault-rails-gem-to-a-plugin/173291)._