Page Menu
Home
Phorge
Search
Configure Global Search
Log In
Files
F117758667
why-multiple-parameterized-classes.rst
No One
Temporary
Actions
View File
Edit File
Delete File
View Transforms
Subscribe
Flag For Later
Award Token
Authored By
Unknown
Size
616 B
Referenced Files
None
Subscribers
None
why-multiple-parameterized-classes.rst
View Options
..
_puppet-module-kolab-why-multiple-parameterized-classes:
=======================================
Why Use Multiple Parameterized Classes?
=======================================
When two nodes provide a part of the same or similar service, such as an
IMAP frontend and an IMAP backend, it is desirable to allow them to have
different configuration, while their individual configuration is
generated from the same template.
One example is the
:man:
`imapd.conf(5)`
``configdir``
setting, which on
IMAP frontends is a happy default, but is usually under the same
directory hierarchy as meta- and spool-partitions.
File Metadata
Details
Attached
Mime Type
text/plain
Expires
Apr 4 2026, 9:54 AM (4 w, 2 d ago)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
18823560
Default Alt Text
why-multiple-parameterized-classes.rst (616 B)
Attached To
Mode
rD docs
Attached
Detach File
Event Timeline