# Distributing custom modules and plugins

**URL:** <https://forum.ansible.com/t/distributing-custom-modules-and-plugins/16572>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [October 21, 2014, 2:28pm UTC](https://forum.ansible.com/t/distributing-custom-modules-and-plugins/16572 "2014-10-21T14:28:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hagai\_Kariti](https://avatars.discourse-cdn.com/v4/letter/h/4491bb/32.png) [@Hagai\_Kariti](https://forum.ansible.com/u/Hagai_Kariti)\
**Post date:** [October 21, 2014, 2:28pm UTC](https://forum.ansible.com/t/distributing-custom-modules-and-plugins/16572/1 "2014-10-21T14:28:12Z")

</div>

Hi

Is there a good way (i.e. something like ansible-galaxy) to distribute custom modules and plugins (filter\_plugins, etc)?

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [October 22, 2014, 3:50am UTC](https://forum.ansible.com/t/distributing-custom-modules-and-plugins/16572/2 "2014-10-22T03:50:28Z")

</div>

Galaxy can take modules in the “./library” path of a role, but IIRC not plugins.
