X-Git-Url: https://scripts.mit.edu/gitweb/wizard.git/blobdiff_plain/ad795d92aed9f47636c46a2a4604253be06eb526..590a90d887a582be6f24d73f57f9df4ff99a0ce8:/TODO diff --git a/TODO b/TODO index 2420ca6..a351d0b 100644 --- a/TODO +++ b/TODO @@ -1,26 +1,39 @@ -The Git Autoinstaller - -TODO NOW: - -- Add support for mypristine workflow -- Make a nicer backtrace if not in a Git working copy directory -- 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 - -- Plugin architecture - http://peak.telecommunity.com/DevCenter/setuptools#dynamic-discovery-of-services-and-plugins - http://peak.telecommunity.com/DevCenter/PkgResources#entry-points - https://xvm.mit.edu:1111/trunk/packages/invirt-base/python/invirt/authz.py - https://xvm.mit.edu:1111/trunk/packages/xvm-authz-locker/setup.py - http://pylonshq.com/docs/en/0.9.7/advanced_pylons/entry_points_and_plugins/ +- [SCRIPTS] MediaWiki 1.9.3 and 1.6.7 + +- .wizard/url semantics are subtly wrong: in particular, if we + explicitly configure a URL at install, we should be able to + detect this URL as baked in from the configuration + +- gct has accidentally set the +x bit on a lot of files >.>. +- Make gct do the right thing with no arguments +- Rerere support doesn't actually work +- Utility scripts gct should support multiple filenames +- "Version 3.0.0 doesn't exist; did you mean 3.0?" +- util.fetch() should use urllib under the hood, not httplib. Code + has to be changed. We should log if we get redirected. +- Be a little more intelligent when perform web checks; for example, + if we get a forbidden message, that probably means we go the right + address but it's blocked off; if we get a 404 message, that probably + means wrong address. Account Unknown is something particularly good + to check for. +- Wordpress module can do something intelligent if we get redirected + to the installation page. +- The need to run egg_info can make things a little fragile when pulling + if you forget. How can we make this less easily forgotten? +- wizardResolve* files seem to get left in tmp en-mass, and we don't + know why. + +- Plugin-ify! Hook-ify! In more detail, applications should all be moved + out into plugins, scripts specific behavior should be moved into + plugins, and hooks need to be made available so that we can exert + the correct level of control. + +- [SCRIPTS] 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. @@ -31,33 +44,27 @@ TODO NOW: - 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) +- [SCRIPTS] 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. -- 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 - 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. +- [SCRIPTS] Web application for installing autoinstalls has a hard + problem with credentials (as well as installations that are not + conducted 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 - 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 - - 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 + - Add support for mypristine workflow - 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 @@ -70,27 +77,16 @@ TODO NOW: 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: +- [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. - -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 + - 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. + - Whatever happens here should be used to improve user.email() + +[ XXX: metadata.rst ] COMMIT MESSAGE FIELDS: @@ -106,38 +102,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 + - get-homedirs.sh. which needs to be run as root on scripts. Store + in /mit/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 - - 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; @@ -160,30 +135,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