Since the "pidfile" param has been added to the list of params for which
root_dir is prepended, editing the pidfile is no longer necessary when
running from a recent git checkout. Added a note to clarify this.
I noticed earlier tonight when I added some information to the "hacking"
docs that my "root_dir" and "sock_dir" links were not actually linking
to anything, and found that they were missing from the minion
configuration page. It turns out that there were a good many params that
hadn't made their way into the docs yet, so I added as many of them as
I could identify.
1) Added an example for the minion config option "providers".
2) Cleaned up line widths on solaris install instructions, and added
information on how to use pkgutil as the default package provider.
3) Since systemd is the default provider for Arch Linux now, I corrected
the information in the "State Providers" page so that the example of
overriding the service provider reflects the current state of the
codebase.
Running pip install -e /path/to/git/clone from within the virtualenv
does not also install salt's additional required modules, as the
document suggests. I ran into this issue last week and so did a guy I
was helping troubleshoot in #salt.
Also, I clarified the bit about using --system-site-packages in your
virtualenv.
Added links to module function documentation, as well as to
"file_roots", and mentioned the saltutil.sync_* functions. Will probably
do the same for returners and renderers soon. This should help people
navigate through the docs easier.
Thanks to s0undt3ch for suggesting this. Anything to type less on the
command line :)
Also, the filenames for the master and minion templates are "master" and
"minion", not "master.template" and "minion.template". Corrected this.
Salt has a lot of Arch Linux users (after all, Arch is the best!), so
I added some information on building the docs in Arch where the python2
version of sphinx-build is called sphinx-build2
Also, when setting up a standalone development environment in a
virtualenv, unless you are running as root (and the docs explicitly
direct you not to do so) you will not have write access to /var/run in
order to create the pidfile. So, the --pid-file argument should be used
to specify a different path.
Finally, a note on running the master and minion in the foreground in
debug mode was added.
