32a104d104
propellor spin
2015-01-01 12:41:24 -04:00
bc5cbee380
propellor spin
2014-12-31 13:22:08 -04:00
d27b638eae
propellor spin
2014-12-31 13:17:45 -04:00
6d4f2b54a6
propellor spin
2014-12-31 13:15:09 -04:00
5374708b6c
propellor spin
2014-12-31 12:59:11 -04:00
95cdedc098
propellor spin
2014-12-31 12:53:11 -04:00
bce6ef5745
propellor spin
2014-12-31 11:43:57 -04:00
2dbd95f9fa
change repo url
2014-12-27 00:20:06 -04:00
28596064c2
layout
2014-12-26 15:35:17 -04:00
c7aac0b35e
remove screen workaround
...
Turns out elephant's oldusenet shellbox docker instance somehow had a
non-setguid screen binary. Dunno how; reinstall fixed it.
2014-12-23 15:45:35 -04:00
35ccb0fac6
fix screen dir mode
2014-12-23 15:29:23 -04:00
9b9a3d6ea1
propellor spin
2014-12-23 14:23:17 -04:00
a48f5916e1
propellor spin
2014-12-23 14:22:50 -04:00
b8be8c244e
propellor spin
2014-12-22 17:16:52 -04:00
26a4c164e4
gitriddance
2014-12-22 15:05:05 -04:00
81db68814c
prep release
2014-12-21 21:41:26 -04:00
dc36a98fc1
Revert ensureProperty warning message, too many false positives in places where Info is correctly propigated. Better approach needed.
2014-12-21 21:33:03 -04:00
7f35024ef2
propellor spin
2014-12-21 21:28:22 -04:00
69b546400c
propellor spin
2014-12-21 21:23:07 -04:00
d194765e10
propellor spin
2014-12-21 21:14:11 -04:00
9444326c87
propellor spin
2014-12-21 21:05:12 -04:00
d38017a1ab
propellor spin
2014-12-21 21:01:46 -04:00
ddeee3ceb8
prep release
2014-12-17 16:30:54 -04:00
8588629034
comment
2014-12-15 12:05:06 -04:00
68714dfd31
propellor spin
2014-12-14 16:15:24 -04:00
333e83a032
propellor spin
2014-12-14 16:15:10 -04:00
23399416f1
broke up big function to describe PrivDataField
2014-12-14 16:14:05 -04:00
71723ca09f
support for crypted passwords in privdata
...
* Added CryptPassword to PrivDataField, for password hashes as produced
by crypt(3).
* User.hasPassword and User.hasSomePassword will now use either
a CryptPassword or a Password from privdata, depending on which is set.
2014-12-14 15:24:10 -04:00
2e2438ae66
improve haddock formating of filenames
2014-12-09 14:22:37 -04:00
3c48f6ac93
remove propelor.1 from the cabal file
...
This file is now generated by building the package.
2014-12-09 00:39:28 -04:00
b22201e36b
Fix Apache.siteEnabled to update the config file and reload apache when configuration has changed.
2014-12-09 00:34:24 -04:00
f8943c2036
fix a case where fileProperty reported a change despite not making one
...
The problem occurred because two lists of lines of the file can be
different, while representing the same file content. For example:
["foo", "bar"]
["foo\nbar"]
2014-12-09 00:30:04 -04:00
040a5fe3c7
prep release
2014-12-09 00:05:16 -04:00
99bff87440
Include Propellor.Property.OS, which was accidentially left out of the cabal file in the last release.
2014-12-09 00:03:14 -04:00
834a05e25a
refactor
2014-12-08 01:22:29 -04:00
06975ec5e1
another place to use toResult
2014-12-08 01:12:55 -04:00
6b6d5a0881
changelog
2014-12-08 01:08:40 -04:00
3c7219874b
finished accidentially committed bit
2014-12-08 01:07:31 -04:00
4e9b01a8a7
propellor spin
...
(cherry picked from commit 1d02d589c7
2014-12-08 01:07:25 -04:00
42a0c83248
Display a warning when ensureProperty is used on a property which has Info and is so prevented from propigating it.
...
Would much rather a type-based fixed, but this is all I have for now.
2014-12-07 17:09:55 -04:00
5a932c382d
docuemnt info propigtion problem
2014-12-07 16:37:02 -04:00
d7d833b431
fix cron example
2014-12-07 15:34:29 -04:00
f9958e1611
prep release
2014-12-07 15:24:07 -04:00
2fe0b28982
more uses for hostContext
2014-12-07 15:21:55 -04:00
3b0b6f44dd
improve
2014-12-07 15:20:50 -04:00
089b7131a6
caution
2014-12-07 15:13:28 -04:00
9ca332e481
Fixed privdata introspection for User.hasPassword and User.hasSomePassword
...
This is not a complete fix for the problem that Info doen't propigate
from the called property when code does something like:
do
hostname <- asks hostName
ensureProperty $ foo hostname
Instead, I just eliminated the need to implement hasPassword that way,
by making the PrivData Info use a HostContext which automatically
gets the right hostname passed to it.
All other uses of withPrivData don't have the problem. It's still possible
for the user to run into the problem if they write something like the
above, where foo is a property that uses privdata. However, all properties
that take a Context now also accept a HostContext, so it's at least less
likely the user needs to write that.
2014-12-07 15:03:06 -04:00
8c12047b6b
simplify using makeChange
2014-12-07 14:49:12 -04:00
6a906c8a4c
typo
2014-12-07 12:50:40 -04:00
dd40a05ced
update
2014-12-06 16:15:08 -04:00
Joey Hess
Joey Hess