# Installing a git-based gem from a discourse plugin

**URL:** <https://meta.discourse.org/t/installing-a-git-based-gem-from-a-discourse-plugin/238657>\
**Category:** Development\
**Created:** [September 10, 2022, 7:05pm UTC](https://meta.discourse.org/t/installing-a-git-based-gem-from-a-discourse-plugin/238657 "2022-09-10T19:05:08Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sreinert](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sreinert/32/103737_2.png) [@sreinert](https://meta.discourse.org/u/sreinert)\
**Post date:** [September 10, 2022, 9:37pm UTC](https://meta.discourse.org/t/installing-a-git-based-gem-from-a-discourse-plugin/238657/3 "2022-09-10T21:37:24Z")

</div>

Thank you! Since this is still under development, I’ll start with the private rubygems server until I can prove that it’s going to work.

I’m curious about why the `>> Gemfile` method is a hack. It’s used in several of the files in the `templates/import/*.yml` for gems that require extra setup. Is that way of doing it considered off limits for regular configurations like this?

---

_[View the full topic](https://meta.discourse.org/t/installing-a-git-based-gem-from-a-discourse-plugin/238657)._