Differences

This shows you the differences between two versions of the page.

--- website_migration [2010/11/11 21:42] – add some documentation to how other parts of the site work dbs
+++ website_migration [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== 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. The new server will in addition host the mailing list, jabber server and other new features to help the community.
+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 [[http://lupin.georgialibraries.org/|lupin.georgialibraries.org]]
 ==== Check List ====
-  * phasefx has proof-of-concepted wiki and blog migration
+  * phasefx has proof-of-concepted [[zzz_archive:website_migration:wiki| wiki]] and [[zzz_archive:website_migration:blog| 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
@@ Line 16: / Line 17: @@
     * 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.