fileserver.conf file configures custom static mount points for Puppet’s file server. If custom mount points are present,
file resources can
access them with their
When to use
This file is necessary only if you are creating custom mount points.
Puppet automatically serves files from the
files directory of every module, and most users find this sufficient.
For more information, see Modules
fundamentals. However, custom mount points are useful for things that you
don’t store in version control with your modules, like very large files and
fileserver.conf file is located
default. Its location is configurable with the fileserverconfig
The location of the
confdir depends on your
operating system. See the confdir
documentation for details.
# Files in the /path/to/files directory are served # at puppet:///extra_files/. [extra_files] path /etc/puppetlabs/puppet/extra_files allow *
fileserver.conf file would create a
new mount point named
fileserver.conf uses a one-off format that
resembles an INI file without the equals
It is a series of mount-point stanzas, where each stanza consists of:
[mount_point_name]surrounded by square brackets. This becomes the name used in
puppet:///URLs for files in this mount point.
path <PATH>directive, where
<PATH>is an absolute path on disk. This is where the mount point’s files are stored.
Deprecated security directives
fileserver.conf could use
deny directives to control which nodes can access various files. This
feature is now deprecated, and will be removed in a future release of Puppet.
Instead, you can use
auth.conf to control
access to mount points. See setting up mount
points for more details and examples.
The only security directive present in
fileserver.conf is an
* directive for every mount point.