TODO NOW:
-- Test code should auto-nuke the database using `wizard remove` before doing a new install
-- git diff :1:$file :2:$file to find out what the user did, or is it :3:?
-- Document how to fix a broken upgrade
-- php.ini needs to get substituted!
-- Make wizard install accept appname-head (so that you can do a test with
- head, and do things without tags). Also make it accept commit hashes.
- In fact, let it accept any committish. Figure out what to do if we
- do a test script with x.y.z when we REALLY mean x.y.z-scripts. XXX!!!
-- Do early validation of inputs for configuration
-- Let 'wizard configure' be interactive
-- Parse output HTML for class="error" and give those errors back to the user,
- then boot them back into configure
+- XXX: Upgrades don't pull updated tags, breaking git describe --tags!
+ Fix this for the future, and figure out how to make everyone else happy!
+- XXX: Some installs are throwing spurious errors; investigate
+- XXX: Prolly would be nice to have some information about how many installs actually succeeded
+- 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.
+
+- 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.
- Pre-emptively check if daemon/scripts-security-upd
is not on scripts-security-upd list (/mit/moira/bin/blanche)
-- Redo Wordpress conversion, with an eye for automating everything
- possible (such as downloading the tarball and unpacking)
-
- Web application for installing autoinstalls has a hard problem
with credentials (as well as installations that are not conducted
- on an Athena machine.) Possible solutions include asking the user
- to SSH into an athena machine and run a bunch of commands, or writing
- a Java applet (possibly in Clojure or Scala) which gets filesystem
- permissions and then performs the operations.
+ on an Athena machine.) We have some crazy ideas involving a signed
+ Java applet that uses jsch to SSH into athena.dialup and perform
+ operations.
- Pay back code debt
- - Genericize callAsUser and drop_priviledges in shell
+ - Tidy up common code in callAsUser and drop_priviledges in shell
- 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
Example: :func:`wizard.app.php.re_var`
- The TODO extension for Sphinx doesn't properly force a full-rebuild
- Code annotation!
- - Make single user mass-migrate work when not logged in as root
+ - Make single user mass-migrate work when not logged in as root. The
+ primary difficulty is making the parallel-find information easily
+ accessible to individual users: perhaps we can do a single-user
+ parallel-find on the fly.
- Don't use the scripts heuristics unless we're on scripts with the
AFS patch. Check with `fs sysname`
- Make 'wizard summary' generate nice pretty graphs of installs by date
- A .scripts directory, with the intent of holding Scripts specific files
if they become necessary.
+ - .scripts/dsn, overriding database source name
+