-
-.. supplement:: Conversions
-
- One of Wizard's goals is to replace the previous autoinstaller infrastructure.
- These boxes will explain extra steps that you must perform in order to carry
- out a conversion of old-style autoinstalls to a Wizard autoinstall.
- In brief, pre-wizard autoinstalls live in :file:`/mit/scripts/deploy` and
- consist of a tarball from upstream, possibly a scripts patch, and possibly
- some post-install munging (such as the creation of a :file:`php.ini` file
- and appropriate symlinks). Performing a conversion means that we will
- recreate these changes in our Wizard autoinstall, and you will start you
- repository with the *earliest* version of the application extant on our
- servers.
-
-Setup
------
-
-Probably the easiest way to do development is entirely on :term:`AFS`: all
-of your source code should live in publically readable (i.e.
-``system:anyuser`` as read permissions) directories, so that if you
-SSH into a scripts server to perform testing, you will be able
-to invoke your tools and read your development repository. In order
-to be able to run the test scripts in the tests directory, this
-is preferably in :file:`web_scripts`. In that
-case, setup is as simple as::
-
- git clone /mit/scripts/git/wizard.git /mit/$USER/web_scripts/wizard
- athrun consult fsr /mit/$USER/web_scripts/wizard system:anyuser read
- # for any application you're going to do development on, also:
- git clone /mit/scripts/git/autoinstalls/$APP.git /mit/$USER/web_scripts/wizard/srv/$APP
-
-If you'd like to be able to develop offline, just note that you will
-have to push your changes to AFS once you start doing testing on
-scripts servers, but before your changes get incorporated into
-canonical upstream. Git doesn't exactly make this easy, but you
-can follow this recipe::
-
- git clone /mit/scripts/git/wizard.git ~/wizard
- cd /mit/$USER
- mkdir wizard.git
- cd wizard.git
- git init --bare
- cd ~/wizard
- git remote add afs /mit/$USER/wizard.git
- git push -f afs master
- git clone /mit/$USER/wizard.git /mit/$USER/wizard
-
-And then you can perform updates from your local copy with::
-
- git push afs master
- cd /mit/$USER/wizard
- git pull
-
-If :file:`/mit/$USER/wizard.git` has write permissions for
-``system:scripts-security-upd``, this is especially useful if you were hacking
-on a copy living on ``not-backward.mit.edu``, and now need to transfer the
-changes back to the canonical repository (please don't give ``not-backward.mit.edu``
-your root tickets!) You can also setup a wizard directory similar to the
-first set of directions for on-server testing.