Here are some things from the TODO file.
Brain-dump:
Perhaps this is just ~/.fabricrc or maybe we want a ~/.braidrc instead.
Or maybe we don't actually need a config file. We just point things at dornkirk,
and override on the command file.
-
Also, how do ~/start scripts then invoke twistd? This is the part of the fancy
initscript wrapper that seems the most useful. But I think it only needs to be
a couple of lines. (Or maybe a few more, but clearer lines of
twisted.python.usage.)
-
Implemente other services.
-
Do we want to verify that stuff is installed, before doing the service install then?
-
Something that would be nice for testing is the ability to specify a
non-default repo for update commands. I'd like to be able to test against a
commit in a local repo, without having to push to a public repo first.
-
Coding-style fixes
- docstings
- camelCase
- Other fabric/braid specific style guidelines?
Future stuff:
- Automatic maintence log generation?
- Alternate handling of ssh-keys not using 'Match Group'?
- Perhaps useful for buildslaves.
Here are some things from the TODO file.
Brain-dump:
Perhaps this is just
~/.fabricrcor maybe we want a~/.braidrcinstead.Or maybe we don't actually need a config file. We just point things at dornkirk,
and override on the command file.
Also, how do ~/start scripts then invoke twistd? This is the part of the fancy
initscript wrapper that seems the most useful. But I think it only needs to be
a couple of lines. (Or maybe a few more, but clearer lines of
twisted.python.usage.)
Implemente other services.
Do we want to verify that stuff is installed, before doing the service install then?
Something that would be nice for testing is the ability to specify a
non-default repo for update commands. I'd like to be able to test against a
commit in a local repo, without having to push to a public repo first.
Coding-style fixes
Future stuff: