Jump to content

FeministWiki:Server setup: Difference between revisions

Line 322: Line 322:
At this point you should test everything using the feministwiki.dev domain name.
At this point you should test everything using the feministwiki.dev domain name.


Some things may not work because they're hard-coded to work as "feministwiki.org" and not under the "feministwiki.dev" name.  This is a point of future improvement: all the services should be configured, if at all possible, in a way that they will work when invoked as feministwiki.dev just as well.
Some things may not work correctly because they're hard-coded to work as "feministwiki.org" and not under the "feministwiki.dev" name.  Here's a list of known issues related to this:
 
* WordPress normally redirects clients to the canonical address of a blog if it's visited through an alternative domain name.  This means we get redirected back to the old server if we try to visit {{C|blogs.feministwiki.dev}}.  To work around this, we use {{C|RequestHeader set Host}} in the Apache2 site configuration, which fools WordPress into believing it's being accessed through the canonical domain name.  Still, the HTML/CSS/JS sent back to the browser refers to some resources on the {{C|.org}} domain, which then fail to load due to CORS violation.
 
If you want to be extra thorough, you can edit your {{C|/etc/hosts}} file to make {{C|feministwiki.org}}, various {{C|*.feministwiki.org}} subdomains, and maybe even other aliases (such as {{C|fem.wiki}}) point to the new server, and then test the few stubborn services that won't otherwise play nice.


=== Deactivate again ===
=== Deactivate again ===