47fb1e451a
sheesh, hopefully this is "most" of it..although definitely still not all we need yet..
36 lines
1.1 KiB
ReStructuredText
36 lines
1.1 KiB
ReStructuredText
|
|
.. highlight:: ini
|
|
|
|
==================
|
|
Other Approaches
|
|
==================
|
|
|
|
Here are some variations on the config theme which you may find
|
|
useful.
|
|
|
|
|
|
Leveraging Site-Wide Config
|
|
===========================
|
|
|
|
It is possible to maintain a single "site-wide" config file, which
|
|
your "machine-wide" config inherits from (see :ref:`site-wide-config`
|
|
and :ref:`config-inheritance`).
|
|
|
|
If you do this, it usually means that your Linux server is running
|
|
Samba and exposing a share which includes the site-wide config
|
|
file(s). We will assume that scenario here, but we assume that part
|
|
is already setup - it will not be described.
|
|
|
|
So let's assume then that you have a Linux server named
|
|
``poser-server`` and it exposes a ``rattail`` share, with a ``config``
|
|
folder and ``site.conf`` within that. So then in your machine-wide
|
|
config on the Windows side, you include it by adding this to
|
|
``C:\ProgramData\rattail\rattail.conf``::
|
|
|
|
[rattail.config]
|
|
include = \\poser-server\rattail\config\site.conf
|
|
|
|
If you do this then you can also *remove* (most) anything from your
|
|
machine-wide config file, which is also defined in the site-wide
|
|
config file.
|