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--