jhaals
commented
8 years ago Hi Paul,
Our solution was to have one server handle the syncing of public modules and then rsync to the rest of the mirrors before taking them online but I'm open to adding proxy support if you feel like implementing it.
Best, Johan
I'm opening this up to start a conversation about potentially adding the ability to proxy requests to another forge, such as the Puppet public forge.
My use case is as following.
Currently, I'm using puppet-anvil and puppet-forge-mirror (thanks for putting those out there!) to successfully serve up privately developed modules as well as modules from the forge. However, there is a period of time from whenever the forge server comes up and when puppet-forge-mirror gets a complete mirror of the public forge. During that time, any hosts that come online would have a pretty good chance of not being able to have a successful puppet run. I'm also anticipating some issues with running the puppet-forge-mirror periodically (daily most likely) and an update to a module gets pushed to the forge, but is unavailable in my mirror until the next puppet-forge-mirror run.
I'm toying with the idea of adding optional proxy support to help with this use case. If the module/release is unavailable, then proxy the request to the user-configured forge.
I haven't given too much thought to the implementation, but it seems doable.
What are your thoughts?
Thanks! Paul