Has anybody had any luck deploying multiple sites (mysite1.com,
mysite2.com) from one radiant install, using IIS?
I’ve attempted using the virtual domain plugin/patch
http://theplant.jp/blog/2006/07/27/radiant-virtual-domain-plugin and
the IIS → mongrel strategy advocated at
Deployment Strategies for Rails on Windows servers | New Auburn Personal Computer Services LLC but I’m having a hard time
using multiple sites with the reverse proxy plugin.
It seems that the reverse proxy plugin only comes into play when rails
is asked to generate a url - whereas the patch included with the
virtual domain plugin changes how radiant generates a url. That’s
about as much as I can figure out thusfar.
Any help appreciated.
–
Mark A. Yoon
[email protected]
On Mar 22, 2007, at 3:07 AM, Mark A. Yoon wrote:
Has anybody had any luck deploying multiple sites (mysite1.com,
mysite2.com) from one radiant install, using IIS?
Ug. Well, I have Radiant working on multiple domains anyway. Not so
much with the using IIS though.
It seems that the reverse proxy plugin only comes into play when rails
is asked to generate a url - whereas the patch included with the
virtual domain plugin changes how radiant generates a url. That’s
about as much as I can figure out thusfar.
I don’t know too much about the reverse proxy plugin, but I’m
intimately familiar with the virtual domain plugin, having updated it
to a 0.6 extension.
The virtual domain plugin (and extension) basically alters Radiant to
have multiple roots, based on the request hostname. So if your root
page is a virtual domain page, and you have “site1” and “site2” as
children (and no config), then /site1/about will actually be /about
for site1.com (or site1.example.com) and /site2/about will be /about
for site2.com (or site2.example.com). So unless your not using
Radiant for the root of your webpage (it’s under /radiant/ or
similar), I don’t see a reason why you’d need the reverse proxy
plugin. Radiant produces URLs like “/about” not “http://example.com/
about”.
If you can explain in a bit more detail the problem(s) you’re having,
I can take a stab at figuring it out.
~~ Brian
Brian,
Thanks for your reply.
So, I am using IIS 6 → ISAPI Rerwrite (Helicon) with proxy rule :
RewriteProxy (?!.*images|.*stylesheets|.javascripts)(.)
http://localhost:4001$1 [I,U]
and your Virtual Domain plugin.
So, I can get two websites and the admin interface to work briefly.
But it seems that once a page gets cached, I can no longer access it.
That is, I can get site1.com, but when I reload it, I get a blank
screen.
Thanks again,
–
Mark A. Yoon
Senior Web Applications/Software Engineer, Northwestern Radiology
[email protected]
Brian,
Thanks for leading me in the right direction with the index caching
(by the way, I’m not having trouble with the admin site, just trouble
with forming coherent sentences).
In “cache\site1”, there’s a file called “.yml” instead of the usual
“index.yml” that I see on a regular installation (without the Virtual
Domain plugin).
–
Mark A. Yoon
Senior Web Applications/Software Engineer, Northwestern Radiology
[email protected]
On Mar 27, 2007, at 6:36 PM, Mark A. Yoon wrote:
So, I can get two websites and the admin interface to work briefly.
But it seems that once a page gets cached, I can no longer access it.
That is, I can get site1.com, but when I reload it, I get a blank
screen.
I seem to recall an issue with caching the index page of a site that
ended in a change to Radiant, but darn if I can remember what it was
exactly. As I recall, it’s because Radiant is caching the index page
where the VirtualDomainPlugin is attempting to have a directory.
That said, if you’re having an issue with the admin pages it’s not
that plugin. Have you tried just running an unmodified Radiant
install with that setup? It’ll serve the same pages to both domains,
but it should work. If that doesn’t work, it’s something with IIS
and I can’t really help with that.
~~ Brian
Brian,
I found http://dev.radiantcms.org/radiant/changeset/205, which fixed the
issue.
Thanks for your help and input.
–
Mark A. Yoon
Senior Web Applications/Software Engineer, Northwestern Radiology
[email protected]