propellor

Configs

Go to file

Joey Hess 4f70fceb3a got rid of the Attr -> Attr SetAttr hack, and use monoids for Attr The SetAttr hack used to be needed because the hostname was part of the Attr, and was required to be present. Now that it's moved to Host, let's get rid of that, since it tended to waste CPU.		2014-05-31 20:43:23 -04:00
debian	Propellor's output now includes the hostname being provisioned, or when provisioning a docker container, the container name.	2014-05-31 18:44:49 -04:00
doc	Propellor's output now includes the hostname being provisioned, or when provisioning a docker container, the container name.	2014-05-31 18:44:49 -04:00
privdata	propellor spin	2014-05-26 18:50:10 -04:00
src	got rid of the Attr -> Attr SetAttr hack, and use monoids for Attr	2014-05-31 20:43:23 -04:00
.gitignore	propellor spin	2014-04-04 00:18:51 -04:00
CHANGELOG	changelog	2014-04-01 15:07:07 -04:00
LICENSE	add copyright	2014-05-10 11:13:42 -03:00
Makefile	sort tags	2014-05-19 16:52:06 -04:00
README.md	add basic front page	2014-04-19 15:45:27 -04:00
Setup.hs	fix	2014-03-30 23:39:07 -04:00
config-joey.hs	propellor spin	2014-05-31 18:35:17 -04:00
config-simple.hs	cleanup	2014-04-19 17:16:13 -04:00
config.hs	change joeyconfig back after merging from master	2014-04-19 16:17:47 -04:00
propellor.cabal	propellor spin	2014-05-31 16:48:14 -04:00

README.md

Propellor is a configuration management system using Haskell and Git. Each system has a list of properties, which Propellor ensures are satisfied.

Propellor is configured via a git repository, which typically lives in ~/.propellor/ on your development machine. Propellor clones the repository to each host it manages, in a secure way. The git repository contains the full source code to Propellor, along with its config file.

Properties are defined using Haskell. Edit ~/.propellor/config.hs to get started. There is fairly complete API documentation, which includes many built-in Properties for dealing with Apt and Apache , Cron and Commands , Dns and Docker, etc.

There is no special language as used in puppet, chef, ansible, etc.. just the full power of Haskell. Hopefully that power can be put to good use in making declarative properties that are powerful, nicely idempotent, and easy to adapt to a system's special needs!

If using Haskell to configure Propellor seems intimidating, see configuration for the Haskell newbie.

quick start

Get propellor installed cabal install propellor or apt-get install propellor
Run propellor for the first time. It will set up a ~/.propellor/ git repository for you.
If you don't have a gpg private key already, generate one: gpg --gen-key
Run: propellor --add-key $KEYID, which will make propellor trust your gpg key, and will sign your ~/.propellor repository using it.
cd ~/.propellor/; use git to push the repository to a central server (github, or your own git server). Configure that central server as the origin remote of the repository.
Edit ~/.propellor/config.hs, and add a host you want to manage. You can start by not adding any properties, or only a few.
Pick a host and run: propellor --spin $HOST
Now you have a simple propellor deployment, but it doesn't do much to the host yet, besides installing propellor.

So, edit ~/.propellor/config.hs to configure the host (maybe start with a few simple properties), and re-run step 7. Repeat until happy and move on to the next host. :)
To move beyond manually running propellor --spin against hosts when you change their properties, add a property to your hosts like: Cron.runPropellor "30 * * * *"

Now they'll automatically update every 30 minutes, and you can git commit -S and git push changes that affect any number of hosts.
Write some neat new properties and send patches to propellor@joeyh.name!

debugging

Set PROPELLOR_DEBUG=1 to make propellor print out all the commands it runs and any other debug messages that Properties choose to emit.