When doing a Fedora upgrade (eg, F17->F20), here are some things to check on.

Scripts Infrastructure

• TextPattern?
• Pony
• whois
• logview (for users, mostly)

Web features

• SSL
  • Do we pick the right cert for mit.edu names?
  • Do we pick the right cert for *.scripts.mit.edu names?
  • Do we pick the right cert for scripts-cert and scripts.mit.edu
• Does mod_vhost_ldap, our static config, and Pony (as applicable) still support...
  • Basic user.scripts.mit.edu
  • foo.user.scripts.mit.edu
  • Wildcards (eg, *.isyournewbicycle.csail.mit.edu -- say, scripts.isyournewbicycle.csail.mit.edu)
  • Non-reified sitename.mit.edu
  • A reified vhost (should have been checked as part of the SSL mit.edu names)
  • Our weirder hosts, scripts.mit.edu and scripts-cert.mit.edu

Autoinstalled Apps

You should check what the whole list is by running an autoinstall, but...

• MediaWiki?
• WordPress?
• git repo
• Trac
  • Warning: Trac will offer to do a schema upgrade when first visited from the new distro, so you should do this with a Trac that you don't mind breaking for a while.
• Frameworks
  • Obviously, these can have substantial variation between them, but checking at least one example is maybe a good idea (if for no other reason than to be better at answering questions)
  • TurboGears?
    • Pony
  • Django
    • ​http://ibtsocs.com/
    • ​ASA DB
  • Ruby

Sites to look at

Here are some sites you could take a look at, as examples of what people actually do, that are also moderately prominent.

• ​http://registrar.scripts.mit.edu/visualroomfinder/
• Django: ​https://asa.mit.edu/ (and try logging in)