I guess I’m not completely understanding the question.
Why not just put the WordPress files into your web site’s /blog directory?
A potential problem is the way Rails Capistrano (deployment tool) works. Every time I migrate my Rails app to a new release, a new dir gets created and the current Rails app dir (which is symbolic link maintained by Capistrano) is updated to point to the new dir. I will have to manually move the wordpress dir to the new Rails dir and this is something I wish to avoid if possible. Hope this makes more sense.
@caliwildman Did you ever find a solution? I am facing the same question.
Thanks.
Hi, did you ever find a solution? I am facing the same question.
This is easy to do with Apache:
- Set up an alias for the URL you want wordpress to have.
- Create a proxy pass exception for that path.
- Proxy everything else to Rails.
That will look like this. Taken from my Apache config:
Alias /blog /home/other_content/blog
<Directory /home/other_content/blog>
AllowOverride All
</Directory>
ProxyPass /blog !
ProxyPass / balancer://mycluster/
ProxyPassReverse / balancer://mycluster/
BTW, I’ve uploaded a new WordPress plugin to do single sign-on with Rails. Search for ‘rails’ in the plugin directory.
