Ideally, use packages instead.
But if that is not possible. Put the tarballs on a web server and have the
agents pull the files from there. It will be much faster than puppet
distributing the files and they will not be in the codebase.
On my repo server, I have a directory for tarballs for when this issue comes up.
Steven
Date: Sat, 9 Mar 2013 23:21:06 +0200
Subject: [Puppet Users] serving large files "formally code artifacts" best
practices
From: emamd...@cloud9ers.com
To: puppet-users@googlegroups.com
Hi All, I'd like to know best practices in serving code artifacts "tarballs"
though puppet , I used to serve them using file{} resource but this method
doesn't seem a good way as i have to either include code artifacts "tarballs"
in puppet codebase repository or configuring puppet codebase repository to
ignore such tarballs and providing a way to inject code artifacts in
$pathtopuppet/modules/module_1/files
--
Best Regards,
Eslam Mamdouh El Husseiny
Systems Administrator
Cloud Niners Ltd.
Cellular: (+2) 011 198 40 40
Mansoura: (+2) 050 234 70 81
Cairo: (+2) 022 268 34 60
Fax: (+2) 022 268 34 63
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
