cadey
/
propellor
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Configs
808 Commits 1 Branch 0 Tags 6.6 MiB
Haskell 98.5%
Cabal Config 1.1%
Makefile 0.4%
Go to file
Joey Hess 78db4881d8
propellor spin 		2014-05-09 09:43:55 -03:00
Propellor propellor spin 2014-05-09 09:42:45 -03:00
Utility merge from git-annex 2014-04-12 13:32:04 -04:00
debian prep release 2014-04-24 18:10:13 -04:00
doc todo 2014-04-29 16:58:10 -04:00
privdata propellor spin 2014-04-21 11:11:47 -04:00
.gitignore propellor spin 2014-04-04 00:18:51 -04:00
CHANGELOG changelog 2014-04-01 15:07:07 -04:00
GPL cabalized and added a wrapper program 2014-03-30 00:08:02 -04:00
Makefile avoid unnecessary use of cabal 2014-04-24 00:45:39 -04:00
Propellor.hs new more expressive config.hs WIP 2014-04-10 21:13:56 -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-09 09:34:09 -03: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 prep release 2014-04-24 18:10:13 -04:00
propellor.hs add module Mains for picky versions of ghc 2014-05-01 10:48:33 -03: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.

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

  1. Get propellor installed cabal install propellor or apt-get install propellor

  2. Run propellor for the first time. It will set up a ~/.propellor/ git repository for you.

  3. 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.

  4. If you don't have a gpg private key, generate one: gpg --gen-key

  5. Run: propellor --add-key $KEYID

  6. Edit ~/.propellor/config.hs, and add a host you want to manage. You can start by not adding any properties, or only a few.

  7. Pick a host and run: propellor --spin $HOST

  8. 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. :)

  9. 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.

  10. 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.