The 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 source attributes.
When to use fileserver.conf
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
sensitive credentials.
Location
The fileserver.conf file is located at $confdir/fileserver.conf by default. Its location is configurable with the fileserverconfig
setting.
The location of the confdir depends on your operating system. See the confdir documentation for details.
Example
# Files in the /path/to/files directory are served
# at puppet:///extra_files/.
[extra_files]
path /etc/puppetlabs/puppet/extra_files
allow *This fileserver.conf file would create a new mount point named extra_files.
Format
fileserver.conf uses a one-off format that resembles an INI file without the equals (=) signs. It is a series of mount-point stanzas, where each stanza consists of:
-
A
[mount_point_name]surrounded by square brackets. This becomes the name used inpuppet:///URLs for files in this mount point. -
A
path <PATH>directive, where<PATH>is an absolute path on disk. This is where the mount point’s files are stored. -
An
allow *directive.
Deprecated security directives
Before auth.conf existed, fileserver.conf could use allow and 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 allow
* directive for every mount point.