TODO NOW:
+- 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
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.
- 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.
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
- 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
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:
Committer: Real Name <username@mit.edu>
Author: lockername locker <lockername@scripts.mit.edu>
-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;
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
scripts.mit.edu / wizard.git / blobdiff