||2 years ago|
|contrib||4 years ago|
|debian||2 years ago|
|doc||2 years ago|
|executables||4 years ago|
|privdata||2 years ago|
|src||2 years ago|
|.gitignore||6 years ago|
|CHANGELOG||8 years ago|
|LICENSE||7 years ago|
|Makefile||3 years ago|
|README.md||8 years ago|
|Setup.hs||8 years ago|
|config-freebsd.hs||4 years ago|
|config-simple.hs||5 years ago|
|config.hs||2 years ago|
|joeyconfig.hs||2 years ago|
|propellor.cabal||2 years ago|
|stack.yaml||4 years ago|
Propellor is configured via a git repository, which typically lives
~/.propellor/ on your development machine. Propellor clones the
repository to each host it manages, in a
secure way. See
Properties are defined using Haskell in the file
There is fairly complete
which includes many built-in Properties for dealing with
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.
- Get propellor installed on your development machine (ie, laptop).
apt-get install propelloror
cabal install propelloror
cabal unpack propellor; cd propellor-version; stack install
propellor --init; this will set up a
~/.propellor/git repository for you.
~/.propellor/config.hs, and add a host you want to manage. You can start by not adding any properties, or only a few.
propellor --spin $HOST
- Now you have a simple propellor deployment to a host. Continue editing
~/.propellor/config.hsto further configure the host, add more hosts etc, and re-run
propellor --spin $HOSTafter each change.
- Once you have a lot of hosts, and running
propellor --spin HOSTfor each host becomes tiresome, you can automate that.
- Write some neat new properties and send patches!
(Want to get your feet wet with propellor before plunging in? try this)