# Any tutorial for running a local Galaxy server?

**URL:** <https://forum.ansible.com/t/any-tutorial-for-running-a-local-galaxy-server/7186>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [July 9, 2024, 11:13am UTC](https://forum.ansible.com/t/any-tutorial-for-running-a-local-galaxy-server/7186 "2024-07-09T11:13:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![howardjones](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/howardjones/32/4169_2.png) [@howardjones](https://forum.ansible.com/u/howardjones)\
**Post date:** [July 9, 2024, 11:13am UTC](https://forum.ansible.com/t/any-tutorial-for-running-a-local-galaxy-server/7186/1 "2024-07-09T11:13:12Z")

</div>

Can anyone recommend a good tutorial for running a local galaxy server?

---

<div class="post-metadata">

**Author:** ![Thulium-Drake](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/thulium-drake/32/833_2.png) [@Thulium-Drake](https://forum.ansible.com/u/Thulium-Drake)\
**Post date:** [July 9, 2024, 2:39pm UTC](https://forum.ansible.com/t/any-tutorial-for-running-a-local-galaxy-server/7186/2 "2024-07-09T14:39:43Z")

</div>

There’s multiple options available to you:

- Running a Galaxy NG server yourself: [Installation - Galaxy NG](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/usage_guide/installation/)
- Running a local RH PrivateAutomation Hub: [Red Hat Ansible Automation Platform installation guide | Red Hat Product Documentation](https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.4/html/red_hat_ansible_automation_platform_installation_guide/index)
- Running it inside JFrog Artifactory: [GitHub - briantist/galactory: An Ansible Galaxy proxy for Artifactory](https://github.com/briantist/galactory) made by @briantist
- Stashing all objects _somewhere_ in Git and using the following in your requirements.yml

```auto
---
collections:
  - name: 'git+https://git.example.nl/myorg/collection'
    version: 'master' # or whatever version you need
roles:
  - name: 'my_role'
    src: 'https://git.example.nl/myorg/role'
    scm: 'git'
    version: '2.5.1'

```

---

<div class="post-metadata">

**Author:** ![isuftin\_at\_usgs](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/isuftin_at_usgs/32/925_2.png) [@isuftin\_at\_usgs](https://forum.ansible.com/u/isuftin_at_usgs)\
**Post date:** [July 9, 2024, 2:55pm UTC](https://forum.ansible.com/t/any-tutorial-for-running-a-local-galaxy-server/7186/3 "2024-07-09T14:55:17Z")

</div>

Also note that Artifactory has just released an update that allows Ansible Galaxy proxying and Ansible collection storage as first class features - [JFrog Help Center](https://jfrog.com/help/r/jfrog-release-information/artifactory-7.90.1-cloud)

---

<div class="post-metadata">

**Author:** ![howardjones](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/howardjones/32/4169_2.png) [@howardjones](https://forum.ansible.com/u/howardjones)\
**Post date:** [July 9, 2024, 3:02pm UTC](https://forum.ansible.com/t/any-tutorial-for-running-a-local-galaxy-server/7186/4 "2024-07-09T15:02:34Z")

</div>

Thanks! We currently host a handful of local modules on a boring old BLOB storage (with a basic webserver), so I know you can also add

```auto
collections: 
 - name: "https://my-secret-webserver.blah.com/thing-2.1.tar.gz"

```

Sounds like Galaxy NG might be what I want, but the install docs seemed predictably complex… (Ansible: current version is deprecated, new version isn’t ready yet - 😲 )

---

<div class="post-metadata">

**Author:** ![shertel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shertel/32/1241_2.png) [@shertel](https://forum.ansible.com/u/shertel)\
**Post date:** [July 16, 2024, 2:48pm UTC](https://forum.ansible.com/t/any-tutorial-for-running-a-local-galaxy-server/7186/5 "2024-07-16T14:48:15Z")

</div>

> [@Thulium-Drake](#):
>
> Stashing all objects _somewhere_ in Git and using the following in your requirements.yml

This feature can be a shortcut for test purposes (for example, to install a PR against a collection to try it out), but I recommend against it for general use.

Here’s another option available for a tar.gz server that I use for its simplicity [GitHub - sivel/amanda: A simple web application, to mimic the v3 API endpoints for Ansible Galaxy Collections, with no database, just a directory with artifacts](https://github.com/sivel/amanda)

---

<div class="post-metadata">

**Author:** ![monsdar](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/monsdar/32/1688_2.png) [@monsdar](https://forum.ansible.com/u/monsdar)\
**Post date:** [July 9, 2025, 11:12am UTC](https://forum.ansible.com/t/any-tutorial-for-running-a-local-galaxy-server/7186/7 "2025-07-09T11:12:42Z")

</div>

> This feature can be a shortcut for test purposes (for example, to install a PR against a collection to try it out), but I recommend against it for general use.

What speaks against using Git as a storage for collections? The only reason I see is that there’s no easy way to host the docs, but this isn’t as important for a selfhosted Galaxy server anyways.