Hey guys,
I just wanted to give you a follow-up on this topic (maybe somebody will
have the same question in the future).
All ideas have been helpful but fpm is awesome :)
I now build rpm's from software which do need dependencies,
pre/post(un)install scripts etc., but if there's no need for tha
We used Gavin's approach and created a "downloads" mount within Puppet, so
Puppet still handles the file transfer, but it's from a different set of
directories outside of the git repo(s).
Also, for anyone creating .deb / .rpm package files, if you aren't using
'fpm', you should be.
--
You re
You could use Git LFS (Large File Support). Instead of large files clogging
up your Git repo, this will keep them separate, while still allowing you to
work with them like they're Git objects. See
https://www.atlassian.com/git/tutorials/git-lfs/ for a better explanation.
I've not used it with r
Since v2.4.0, r10k allows data to be directed into a specific :install_path
from a git repo in the Puppetfile.
See
https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#per-item-install-path
If you have a separate repo of your "files", you could load that into a
directory in the en
Robert
Whilst not directly what you're trying to achieve, we do something similar
to distribute Java etc by having a separate Puppet fileserver mount called
'software'.
Then anything that needs to consume those files can just use that mount
point...
Cheers
Gavin
On Wednesday, 14 December 2
