TODO NOW:
-- If you try to do an install on scripts w/o sql, it will sign you up but fail to write
- the sql.cnf file. This sucks.
+- Symlinked rerere to get awesomeness. Consider permissions
+- Wordpress needs to get rid of the siteurl hack, so that it actually
+ has a fully-qualified URL http://foo.scripts.mit.edu/blah. This will
+ also fix Wordpress's cron functionality. We should be careful not
+ to write over users who are on vhosts. We should figure out who is
+ still on twiddle paths. We should make sure the redirect is handled
+ correctly.
+- Wizard needs a correct arch/ setup
+- The wizard command, when not on scripts, should automatically SSH to
+ scripts and start executing there?
+- Write the code to make Wordpress figure out its URL from the database
+
+- Remerges aren't reflected in the parent files, so `git diff` output is
+ spurious. Not sure how to fix this w/o tree hackery.
+- Sometimes users remove files. Well, if those files change, they automatically
+ get marked as conflicted. Maybe we should say for certain files "if they're
+ gone, they're gone forever"? What is the proper resolution?
-- wizard install wordpress should ask for password. One problem with this is that
- Wordpress will still send mail with the wrong username and password, so Wordpress
- will need to be patched to not do that. Alternatively we can initally set the admin
- email to a null address and then fix it manually.
-- --raw parameter for install which means an arbitrary commit can be installed
- Parse output HTML for class="error" and give those errors back to the user (done),
then boot them back into configure so they can enter in something different
-- Get rid of our custom sizing code and use dialog's built-in sizing (i.e. width=0, height=0).
- Maybe our sizing code is superior, maybe not.
- Replace gaierror with a more descriptive name (this is a DNS error)
- Pre-emptively check if daemon/scripts-security-upd
is not on scripts-security-upd list (/mit/moira/bin/blanche)
+- If you try to do an install on scripts w/o sql, it will sign you up but fail to write
+ the sql.cnf file. This sucks.
- Web application for installing autoinstalls has a hard problem
with credentials (as well as installations that are not conducted
operations.
- Pay back code debt
- - Tidy up common code in callAsUser and drop_priviledges in shell
+ - Tidy up common code in callAsUser and drop_priviledges in shell;
+ namely cooking up the sudo and environment variable lines
- Summary script should be more machine friendly, and should not
output summary charts when I increase specificity
- - Summary script should do something intelligent when distinguishing
- between old-style and new-style installs
- Report code in wizard/command/__init__.py is ugly as sin. Also,
the Report object should operate at a higher level of abstraction
so we don't have to manually increment fails. (in fact, that should
also be automated.
- Move resolutions in mediawiki.py to a text file? (the parsing overhead
may not be worth it)
- - If a process is C-ced, it can result in a upgrade that has
- an updated filesystem but not updated database. Make this more
- resilient
- PHP end of file allows omitted semicolon, can result in parse error
if merge resolutions aren't careful. `php -l` can be a quick stopgap
- It should be able to handle installs like Django where there's a component
that gets installed in web_scripts and another directory that gets installed
in Scripts.
- - ACLs is a starting point for sending mail to users, but it has
- several failure modes:
- - Old maintainers who don't care who are still on the ACL
- - Private AFS groups that aren't mailing lists and that we
- can't get to
- A question is whether or not sending mail actually helps us:
- many users will probably have to come back to us for help; many
- other users won't care.
+
+- ACLs is a starting point for sending mail to users, but it has
+ several failure modes:
+ - Old maintainers who don't care who are still on the ACL
+ - Private AFS groups that aren't mailing lists and that we
+ can't get to
+ A question is whether or not sending mail actually helps us:
+ many users will probably have to come back to us for help; many
+ other users won't care.
PULLING OUT CONFIGURATION FILES IN AN AUTOMATED MANNER
scripts.mit.edu / wizard.git / blobdiff