X-Git-Url: https://scripts.mit.edu/gitweb/wizard.git/blobdiff_plain/1a8a1f333a3735ab766136ed76462044b5612c4e..6554c6378a6e801b4fe47c50688cdae1d627bc18:/TODO diff --git a/TODO b/TODO index 08ace5d..260941d 100644 --- a/TODO +++ b/TODO @@ -2,7 +2,16 @@ The Git Autoinstaller TODO NOW: -- Write the code to make Wordpress figure out its URL from the database +- If no newlines at all, DON'T CARE (don't rewrite the file again!) +- Plugin-ify! + +- Add support for mypristine workflow +- 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. - Remerges aren't reflected in the parent files, so `git diff` output is spurious. Not sure how to fix this w/o tree hackery. @@ -10,17 +19,9 @@ TODO NOW: 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. - 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 -- 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. @@ -35,22 +36,12 @@ TODO NOW: 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 - - 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 - probably be called something different). The by-percent errors should - also be automated. - - Move resolutions in mediawiki.py to a text file? (the parsing overhead - may not be worth it) - - 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 - Other stuff - Figure out why Sphinx sometimes fails to crossref :func: but wil crossref :meth:, even though the dest is very clearly a function. 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. The primary difficulty is making the parallel-find information easily accessible to individual users: perhaps we can do a single-user @@ -72,18 +63,7 @@ TODO NOW: 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 - -advancedpoll: Template file to fill out -django: Noodles of template files -gallery2: Multistage install process -joomla: Template file -mediawiki: One-step install process -phpbb: Multistage install process -phpical: Template file -trac: NFC -turbogears: NFC -wordpress: Multistage install process +[ XXX: metadata.rst ] COMMIT MESSAGE FIELDS: @@ -99,38 +79,17 @@ GIT COMMIT FIELDS: Committer: Real Name Author: lockername locker -NOTES: - -- It is not required nor expected for update scripts to exist for all - intervening versions that were present pre-migration; only for it - to work on the most recent migration. - -- Currently all repositories are initialized with --shared, which - means they have basically ~no space footprint. However, it - also means that /mit/scripts/wizard/srv MUST NOT lose revs after - deployment. - OVERALL PLAN: +[ XXX: doc/deps.rst ] * Some parts of the infrastructure will not be touched, although I plan on documenting them. Specifically, we will be keeping: - - parallel-find.pl, and the resulting - /mit/scripts/.htaccess/scripts/sec-tools/store/scriptslist - -* The new procedure for generating an update is as follows: - (check out the mass-migration instructions for something in this spirit, - although uglier in some ways; A indicates the step /should/ be automated) - - 0. ssh into not-backward, temporarily give the daemon.scripts-security-upd - bits by blanching it on system:scripts-security-upd, and run parallel-find.pl + - get-homedirs.sh. which needs to be run as root on scripts. Store + in /mit/scripts/sec-tools/store/scriptslist - 1. [ see doc/upgrade.rst ] - - [ENTER HERE FROM CREATING A NEW REPO] - - 9. Push all of your changes in a public place, and encourage others - to test, using --srv-path and a full path. + - parallel-find.pl, and the resulting + /mit/scripts/sec-tools/store/versions [ XXX: doc/deploy.rst ] GET APPROVAL BEFORE PROCEEDING ANY FURTHER; @@ -153,30 +112,7 @@ OVERALL PLAN: 12. Run parallel-find.pl to update our inventory -[ XXX: doc/upgrade.rst ] -* For mass importing into the repository, there are a few extra things: - - * When mass producing updates, if the patch has changed you will have to - do a special procedure for your merge: - - git checkout pristine - # NOTE: Now, the tricky part (this is different from a real update) - git symbolic-ref HEAD refs/heads/master - # NOTE: Now, we think we're on the master branch, but we have - # pristine copy checked out - # NOTE: -p0 might need to be twiddled - patch -p0 < ../app-1.2.3/app-1.2.3.patch - git add . - # reconstitute .scripts directory - git checkout v1.2.2-scripts -- .scripts - git add .scripts - # NOTE: Fake the merge - git rev-parse pristine > .git/MERGE_HEAD - - You could also just try your luck with a manual merge using the patch - as your guide. - -[ XXX: doc/layout.rst ] +[ XXX: doc/metadata.rst ] * The repository for a given application will contain the following files: - The actual application's files, as from the official tarball