This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5ACFC7204709E2EE8146197C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi: I'm still learning the specifics of how to use OpenShift for this purpose, so my steps here are an overview. I'm keeping good notes, which I'll turn in to documentation. * Setup basic MediaWiki on wiki-ovirt.rhcloud.com. (DONE) * Add in extensions and customizations we are keeping. * Load a recent snapshot of the current wiki database. * Load the new theme. * Test how things look. * Figure out how we're going to deal with the /wiki situation. * Change over DNS. Another option is to update the current wiki to use the new theme, deal with the redirects, then do the changeover to OpenShift. Any reason to pick one way over another? The /wiki situation is that our "wiki" is configured following the MediaWiki standard of domain.example.org/wiki. If we're going to make MediaWiki the service behind www.ovirt.org, we're going to need to decide= : * Do we keep or drop the /wiki convention? * How do we handle redirects? ** Is this something OpenShift can do? * Where do we handle redirects for content from Wordpress? ** Do we need individual redirects for each old-URL?!? - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enig5ACFC7204709E2EE8146197C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iD4DBQFQnWmR2ZIOBq0ODEERAvtWAJMHnclMj/kEe6yWw+p42FtUyecCAKCNhxWj MWrgXEJC0mjc9UA0vv49BQ== =CBOU -----END PGP SIGNATURE----- --------------enig5ACFC7204709E2EE8146197C--