Configs
Go to file
Joey Hess f28cdc84fd
foo
2014-03-30 02:48:31 -04:00
Property property lists 2014-03-30 02:28:08 -04:00
Utility use fqdn 2014-03-30 01:17:19 -04:00
GPL cabalized and added a wrapper program 2014-03-30 00:08:02 -04:00
HostName.hs use fqdn 2014-03-30 01:17:19 -04:00
Makefile foo 2014-03-30 02:48:31 -04:00
Propellor.hs rename 2014-03-30 02:37:45 -04:00
Property.hs property lists 2014-03-30 02:28:08 -04:00
README foo2 2014-03-30 02:46:05 -04:00
Setup.hs cabalized and added a wrapper program 2014-03-30 00:08:02 -04:00
TODO password locking 2014-03-30 00:17:44 -04:00
propellor.cabal rename 2014-03-30 02:37:45 -04:00

README

This is a work in progress configuration management system using Haskell
and Git.

Propellor enures that the system it's run in satisfies a list of
properties, taking action as necessary when a property is not yet met.

The design is intentionally very minimal.

Propellor lives in a git repository, and so to set it up it's cloned
to a system, and "make" can be used to pull down any new changes,
and compile and run propellor. This can be done by a cron job. Or something
can ssh in and run it.

For bootstrapping, propellor compiles to a single binary file,
which can be transferred to a host and run.

Properties are defined using Haskell. 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.

Also avoided is any form of node classification. Ie, which hosts are part
of which classes and share which configuration. It might be nice to use
reclass[1], but then again a host is configured using simply haskell code,
and so it's easy to factor out things like classes of hosts as desired.

[1] http://reclass.pantsfullofunix.net/