Installing from source

Use your system's package tools to ensure that the following prerequisites are installed:

• (Optional) Puppet Server 2.x or newer

• A working Puppet agent or server setup (for ssl-setup to succeed)

• Facter, version 3 or newer

• JDK 8 or newer

• Leiningen

• Git (for checking out the source code)

• Rake (version 0.9.6 or newer)

Install Leiningen:

$ mkdir ~/bin && cd ~/bin
$ curl -L 'https://raw.githubusercontent.com/technomancy/leiningen/stable/bin/lein' -o lein --tlsv1
$ chmod ugo+x lein
$ ./lein
# symlink lein to somewhere in your $PATH
$ sudo ln -s /full/path/to/bin/lein /usr/local/bin

Run the following commands to build a distribution tarball from source:

$ mkdir -p ~/git && cd ~/git
$ git clone git://github.com/puppetlabs/puppetdb
$ git checkout stable    # Or a particular tag you wish to install
$ cd puppetdb
$ lein install
$ lein with-profile ezbake ezbake stage
$ cd target/staging
$ rake package:bootstrap
$ rake package:tar

Now unpack the tarball to prepare for installation:

$ cd pkg
$ tar -xzf puppetdb-*.tar.gz
$ cd puppetdb-*

To perform a full installation of the service and the PuppetDB-termini code (usually the best choice when running PuppetDB on the same host as the Puppet Server):

$ sudo bash install.sh all

Otherwise, for service only:

$ sudo bash install.sh service

Or for terminus code only:

$ sudo bash install.sh termini

While installing from source is useful for simply running a development version for testing, for development it's better to be able to run directly from source, without any installation step.

Run the following commands:

$ mkdir -p ~/git && cd ~/git
$ git clone git://github.com/puppetlabs/puppetdb
$ cd puppetdb

# Download the dependencies
$ lein deps

This will let you develop on PuppetDB and see your changes by simply editing the code and restarting the server. It will not create an init script or default configuration directory. To start the PuppetDB service when running from source, you will need to run the following:

$ lein run services -c /path/to/config.ini

A sample config file is provided in the root of the source repo: config.sample.ini. You can also provide a conf.d-style directory instead of a flat config file.

Next, you will need to setup some test users to run the tests locally

In most cases you should set up a PostgreSQL server and configure PuppetDB to use it. You may also need to adjust the maximum heap size.

You can change PuppetDB's database at any time while the service is shut down, but note that changing the database does not migrate PuppetDB's data, so the new database will be empty.

If your PostgreSQL node is on a separate server than PuppetDB, you should configure an SSL connection, otherwise your database communication will happen in plaintext over the network. This can be made much simpler by installing using the PuppetDB module.

If you installed PuppetDB from source, you can start PuppetDB by running the following:

$ sudo service puppetdb start

And if Puppet is installed, you can permanently enable PuppetDB by running:

$ sudo puppet resource service puppetdb ensure=running enable=true

If you are running PuppetDB from source, you should start it as follows:

# From the directory in which PuppetDB's source is stored:
$ lein run services -c /path/to/config.ini

PuppetDB is now fully functional and ready to receive catalogs and facts from any number of Puppet Servers.

You should now configure your Puppet Server(s) to connect to PuppetDB.

If you use a standalone Puppet site, you should configure every node to connect to PuppetDB.