-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reuse existing modules path #50
Comments
Hi! Sorry for the delay and thanks for giving it a try. Could you please list the current content of your modules folder (something like You could start it without daemonizing (e.g. |
ls -la /extra/puppetforge/modules/zuinnote/ ls -la /extra/puppetforge/modules/zuinnote/oraclejdk8/ ls -la modules/adrien/filemapper/adrien-filemapper-1.* As you can see, cache is being populated instead:
This is how I start it: |
Hi,
First of all, great idea! Much easier than figuring out the pulp!
If I understood well, the puppet-forge-server is able to reuse a locally downloaded puppet forge mirror.
I have downloaded the entire puppet forge (1 Gb) by using: https://github.com/jhaals/puppet-forge-mirror/blob/master/lib/puppet-forge-mirror.rb and I have pointed this puppet-forge-server to use the ./modules folder.
Well, it seems it's not able to find them and it's downloading from internet. The modules downloaded are each in it's subfolder, in the format:
./modules/puppetlabs/apache/puppetlabs-apache-1.10.0.tar.gz
This is how I call it:
puppet-forge-server -D -m $base/modules -x https://forgeapi.puppetlabs.com --log-dir $base/log --cache-basedir $base/cache --pidfile $base/server.pid
The text was updated successfully, but these errors were encountered: