Ruby on Rails, mod_proxy subdirectory, and WP_ALLOW_MULTISITE (9 posts)

  1. briansage
    Posted 4 years ago #

    I've had great luck with Doncha's excellent domain mapping plugin since WPMU 2.8, but I've never tried it quite like this...

    1) We have several sites at different domains (foo.com, bar.com, etc.com) that use Ruby on Rails and Apache (already working).

    2) We would like to use Apache's mod_proxy to make foo.com/blog, bar.com/blog, and etc.com/blog all point to our WP VPS at wpblog.com/blog (also, already set up and working)

    3) We would like these WP instances to be a single WP_ALLOW_MULTISITE installation that runs from that location and is domain-mapped to serve these domains as separate subdirectory installations.

    Has anyone ever done something like this, using domain mapping?

  2. is domain-mapped to serve these domains as separate subdirectory installations.

    Yes, I have done it, but you don't use the domain mapping plugin.

    You use a multi *network* plugin.


  3. briansage
    Posted 4 years ago #

    Thanks Andrea! I'm getting one...

  4. briansage
    Posted 4 years ago #

    Thanks for the advice. This seemed to work at first blush, but pretty permalinks aren't working, now that we're testing content.

    My suspicion is that permalinks need to be setup in the master network, then settings need to be cloned and remain unchanged. Does that sound right?

  5. no.

    Sub sites can have completely different permalink setting than the main site. they are *independent* from site to site.

    If your permalinks aren't working, it's still an htaccess issue. I bet your media uploads aren't working either.

  6. briansage
    Posted 4 years ago #

    Yeah, nothing is working well at this point. Even / is a WP 404, while we have posts. We've given up on the multisite, all together, until we can get this working correctly.

    I think the big issue is that we have sitedomain.com/blog/ (Ruby on Rails project on Apache) using mod_proxy to grab content from blogserverIP/sitename/ (WP single install on Apache). Somewhere in all that, it's going awry.

  7. Yeeeaaaaahhhh.... somewhere in there it's all going to pot. outside of anything multisite.

  8. briansage
    Posted 4 years ago #

    Finally got a single site install to work (brilliantly, I might add). The trick we had to overcome was our path vs. directory discrepancy, and we sort of did it by lying to the server... We added a ServerAlias that matched the production site's and pointed our hosts files to it during setup :P

    Thanks again for all the help. I'll be giving multisite another shot after we prove a few things with this setup.

  9. Hey, whatever works. :D

Topic Closed

This topic has been closed to new replies.

About this Topic