summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2017-03-18more old ghc fixesJoey Hess
2017-03-18Fix build with pre-AMP ghc.Joey Hess
2017-03-18Merge branch 'master' into joeyconfigJoey Hess
2017-03-18Fix build with pre-AMP ghc.Joey Hess
2017-03-18propellor spinJoey Hess
2017-03-18propellor spinJoey Hess
2017-03-18propellor spinJoey Hess
2017-03-18propellor spinJoey Hess
2017-03-18propellor spinJoey Hess
2017-03-18setting up joeyconfig after mergeJoey Hess
2017-03-18propellor spinJoey Hess
2017-03-18propellor spinJoey Hess
2017-03-18propellor spinJoey Hess
2017-03-15descJoey Hess
2017-03-15add news item for propellor 4.0.0Joey Hess
2017-03-15more changelogJoey Hess
2017-03-15prep releaseJoey Hess
2017-03-15Added Monoid instances for Property and RevertableProperty.Joey Hess
* Added Monoid instances for Property and RevertableProperty. * Removed applyToList. Instead, use mconcat. (API change) Eg, if you had: applyToList accountFor [User "joey", User "root"] use instead: mconcat (map accountFor [User "joey", User "root"]) mappend x y is basically the same as x `before` y. In particular, if x fails to be ensured, it won't ensure y. This seems to make sense, since applyToList had that behavior, and so does the Monoid for Propellor Result. The alternative would be to try to ensure both and combine the results. However, I don't see any reason to do it that way. It would be nice if the description of both properties were displayed when ensuring the combination. But then, it would need to display eg: ensuring x..ok ensuring y..failed ensuring x and ensuring y..failed Without a way to get rid of that redundant last line, I don't want to do that. Note that the haddocks for the Monoid instances need a really wide screen to display! This is IMHO an infelicity in haddock, and I can't do anything about it really. This commit was sponsored by Fernando Jimenez on Patreon.
2017-03-15Property types changed to use a Maybe (Propellor Result). (API change)Joey Hess
* Property types changed to use a Maybe (Propellor Result). (API change) * When Nothing needs to be done to ensure a property, propellor will avoid displaying its description at all. The doNothing property is an example of such a property. This is mostly in preparation for Monoid instances for Property types, but is's also nice that anything that uses doNothing will avoid printing out any message at all. At least, I think it probably is. It might potentially be confusing for something that sometimes takes an action and sometimes resolves to doNothing and in either case has a description set to not always show the description. If this did turn out to be confusing, the change to doNothing could be reverted. This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
2017-03-11cleanupJoey Hess
2017-03-11doneJoey Hess
2017-03-11don't propagate DNS info from DiskImage chrootsJoey Hess
* DiskImage building properties used to propagate DNS info out from the chroot used to build the disk image to the Host. That is no longer done, since that chroot only exists as a side effect of the disk image creation and servers will not be running in it. * The IsInfo types class's propagateInfo function changed to use a PropagateInfo data type. (API change) This is particularly important when using hostChroot, since the host could well have DNS settings then. This commit was sponsored by Ole-Morten Duesund on Patreon.
2017-03-11Implemented hostChrootJoey Hess
As originally seen in my slides at Linux.Conf.Au 2017 in January. Now that it's not vaporware, it allows one Host to build a disk image that has all the properties of another Host. It was easier than I thought to implement this! As expected, Info propagation was slightly tricky. Also, I originally had a lot of machinery to try to use Info to detect infinitely nested chroot loops. But, my machinery didn't work, and when I tested it, ghc did a much better job, causing a "warning: <<loop>>" message to be output instead of such a property using infinite disk space. This commit was sponsored by Bruno BEAUFILS on Patreon.
2017-03-11Changed Chroot data type to include Info propigationJoey Hess
This will allow for different Chroots that propigate info differently. hostChroot will use this. This commit was sponsored by Peter Hogg on Patreon.
2017-03-11reorg docsJoey Hess
2017-03-11fix exampleJoey Hess
2017-03-08Remove make from propellor's dependency listJoey Hess
It's not used by propellor any longer. Has not been used for a long time actually.
2017-03-08Makefile: Removed "run" target which was default target.Joey Hess
"make" now only builds propellor, does not run it. Note that propellor 1.0.0 and earlier relied on this target for the Cron.runPropellor property's cronjob to work, so upgrading directly to this version from 1.0.0 would break that cron job. (Debian has 0.9.1 in stable, and 3.2.3 will be in the next stable release. Upgrading between Debian releases is supposed to be done without skipping a release, so that's ok.)
2017-03-08Merge branch 'joeyconfig'Joey Hess
2017-03-08propellor spinJoey Hess
2017-03-08propellor spinJoey Hess
2017-03-08added Apache.confEnabledJoey Hess
2017-03-07Merge branch 'master' of ssh://propellor.branchable.comJoey Hess
2017-03-07clean up after mergeJoey Hess
2017-03-07Merge branch 'joeyconfig'Joey Hess
2017-03-07updateJoey Hess
2017-03-07propellor spinWalter Franzini
2017-03-06flip arm build times while still bringing up the ancient buildJoey Hess
2017-03-06propellor spinWalter Franzini
2017-03-06propellor spinWalter Franzini
2017-03-04propellor spinEric Schug
2017-03-03propellor spinJoey Hess
2017-03-02setting up joeyconfig after mergeJoey Hess
2017-03-02Merge branch 'master' into joeyconfigJoey Hess
2017-03-01propellor spinJoey Hess
2017-03-01clean up after mergeJoey Hess
2017-03-01Merge branch 'joeyconfig'Joey Hess
2017-03-01use git.joeyh.nameJoey Hess
2017-03-01add news item for propellor 3.4.1Joey Hess
2017-03-01Fixed https url to propellor git repository.Joey Hess