-
Notifications
You must be signed in to change notification settings - Fork 12
Setup config files
d3 needs two config files: one for the ruby-jss module to use for API and MySQL connections, and another for d3 itself.
The files are self-documented, so please read through them to understand all the options.
After editing the files appropriately on your own machine, you'll be deploying them to your managed computers.
Make a copy of the ruby-jss.conf.example file.
-
If you installed d3 with the .pkg it will be in /etc/
-
If you installed with "gem install" it will be in the "data" folder of the newly-installed gem.
(e.g. /Library/Ruby/Gems/2.0.0/gems/ruby-jss-<version>/data/ruby-jss.conf.example)
Open up your copy of ruby-jss.conf.example, and read through it, adding values as appropriate.
IMPORTANT: This is where you'll put the read-only account names you created in "Preparing the servers"
When finished, put your edited copy into /etc/ruby-jss.conf. You'll also eventually be deploying it to your managed computers.
Make a copy of the d3.conf.example file.
- If you installed d3 with the .pkg it will be in /etc/
- If you installed with "gem install" it will be in the d3 support folder at /Library/Application Support/d3/.
Then read through it, adding values as appropriate.
For some useful basic vocabulary, see the Welcome page
IMPORTANT: Credentials for read-write access will be dealt with in Configuring d3admin
When finished, put your edited copy into /etc/d3.conf. You'll also eventually be deploying it to your managed computers.