Website Migration

This is a documentation of the process for migrating data from the old web server to the new one being generously setup by PINES for the community.

Server we are migrating to lupin.georgialibraries.org

• phasefx has proof-of-concepted wiki and blog migration

Note: On Penguin DokuWiki and wordpress were installed from package, on lupin we will install from source.

• go through http://lupin.georgialibraries.org/~csharp/links-evergreen.html
• need to setup a system for backups on the new server
• get folks to test the results
• turn off access to dokuwiki edits and do final migration of data
• set date to flip the DNS switch
• document how different parts of the website work
  • http://planet.evergreen-ils.org/ - Dan Scott currently runs that on his coffeecode.net server (also visible at http://planet-evergreen.coffeecode.net); it's just a simple Planet Venus instance with a slightly customized header. It should be easy enough to check the customizations and configuration file into a repository and have planet.evergreen-ils.org pull the config from there on an hourly basis (or something like that) so that anybody interested in updating the config file would just need to be given commit access to the repository. (Might need to think for a bit about other approaches if automating the pull of that config introduces the possibility of exploits of other stuff running on my server, which would be ++ungood). For now, at least, here's a bzr repo of the current code: http://bzr.coffeecode.net/planet-evergreen/
  • http://docs.evergreen-ils.org - just a DNS entry that points to Robert Souilliere's server; most of their code is at https://github.com/rsoulliere/Evergreen-DocBook/
• tsbere thinks that an occasional "export all the pages and check that into SVN automatically if different" could work for a wiki-ized or CMS-ized site (phasefx likes ILS-Contrib/evergreen-ils.org, because if the "trusted sys admins" ever go insane, then the community could fork wiki-ized the content)
  • tsbere points at https://github.com/zoranzaric/dokuwiki-git-plugin for a way to do that kind of thing on dokuwiki (to git, but should be easily adapted to svn if needed)
• look at wiki-fying or using a CMS the whole site.
• ensure that public_html home directories are correctly setup and available and/or migrate the public_html content to other web-accessible locations.