On Thu, 2012-05-24 at 09:37 -0700, btimby wrote: > I am using puppet in standalone mode (puppet apply) to test manifests > that I also use in a client/server configuration. > > I have everything working as far as files included in modules. I can > reference file source as "puppet:///modules/modulename/path/to/file". > > However, some files are not part of a module, so for the client/server > portion, I just set up a share called files. However, references to > these files "puppet://files/path/to/files" don't work in standalone > mode.
Because it tries to resolve a host called 'files' as the server where to get those files. Have you tried: puppet:///files/path/to/files (notice the ///) > I understand that standalone mode (puppet apply) command can find the > module files because you tell it the path to look in (--modulepath > argument). Why is there no argument for adding file shares > (--fileserver=files:/path/to/files)? Is there another way to achieve > this? > > My workaround for now is to simply move the files to a module named > files and reference them as "puppet:///modules/files/path/to/file", > but it seems like there might be a better solution. You could also setup a puppetmaster only for the purpose of serving files to your servers, and use: puppet://fileserver.domain.com/files/path/to/file kind of url. It's still masterless for compilation purposes, but uses a master for file serving. -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
