Moving MediaWiki to OpenShift
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--
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBD3B70D25BD0D68B6E16B910 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/09/2012 12:37 PM, Karsten 'quaid' Wade wrote:
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 deci= de: =20 * 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?!?
We can use a .htaccess file in the web root: https://openshift.redhat.com/community/kb/kb-e1044-how-to-redirect-traffi= c-to-https We'll have to use the MediaWiki directions to figure out the way to get everything at / instead of /wiki: http://www.mediawiki.org/wiki/Manual:Short_URL http://www.mediawiki.org/wiki/Manual:Short_URL#URL_like_-_example.com.2FP= age_title http://www.mediawiki.org/wiki/Manual:Wiki_in_site_root_directory - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enigBD3B70D25BD0D68B6E16B910 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/ iD8DBQFQna5+2ZIOBq0ODEERArlwAJ4vcIESZpGGWfQ/XbhFKjineikhvQCgzwb7 GIzpvF06u6iLR0CW57s4s6Q= =psBI -----END PGP SIGNATURE----- --------------enigBD3B70D25BD0D68B6E16B910--
Hi Karsten, On 11/09/2012 09:37 PM, Karsten 'quaid' Wade wrote:
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.
Thanks for this! Very useful.
* 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?
A half-way house might be to install the new theme on the current wiki - anyone can then try it, but the daefault will relain the MonoBook theme until we switch to the OpenShift site.
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?
I vote for this - it's the recommended MediaWiki set-up.
* How do we handle redirects? ** Is this something OpenShift can do?
My understanding is that the redirects we need to handle are old links which exist in the WordPress site, and which should point at a wiki equivalent now. Is that correct? If so, I think the easiest way to do it is to do plain text "permanently moved" 301 redirects in Apache's config: Redirect Permanent /old/url /new/url Since we only have about 30 of these to take care of, we should be fine. We might want to do something different for blog type links (the "news" pages) - dependeninf on whether we decide to have a wordpress blog or not in the future (I think we should).
* Where do we handle redirects for content from Wordpress? ** Do we need individual redirects for each old-URL?!?
I don't think it's a lot of work. I'd recomment individual redirects. Thanks, Dave. -- Dave Neary Community Action and Impact Open Source and Standards, Red Hat Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF433B673E51CBCA7801A3049 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/12/2012 02:17 AM, Dave Neary wrote:
=20
* How do we handle redirects? ** Is this something OpenShift can do? =20 My understanding is that the redirects we need to handle are old links which exist in the WordPress site, and which should point at a wiki equivalent now. Is that correct? =20 If so, I think the easiest way to do it is to do plain text "permanentl= y moved" 301 redirects in Apache's config: Redirect Permanent /old/url /new/url =20 Since we only have about 30 of these to take care of, we should be fine= =2E =20 We might want to do something different for blog type links (the "news"=
pages) - dependeninf on whether we decide to have a wordpress blog or not in the future (I think we should). =20
* Where do we handle redirects for content from Wordpress? ** Do we need individual redirects for each old-URL?!? =20 I don't think it's a lot of work. I'd recomment individual redirects.
Can we get those individual redirects written now? What are the pages? - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enigF433B673E51CBCA7801A3049 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 undefined - http://www.enigmail.net/ iD8DBQFQs4vL2ZIOBq0ODEERApPwAJ0UtqDpxfKLSlEQl91kjC8e5j0D4QCgxG8Q k/lN2GZfP+OYKqpXaZUpuM8= =s30Y -----END PGP SIGNATURE----- --------------enigF433B673E51CBCA7801A3049--
participants (2)
-
Dave Neary -
Karsten 'quaid' Wade