Matt,
It isn't a remarkably stupid question but there are a remarkably lot of
options and reasons why to choose one path over another.
Do you have separate backends for a.com and b.com ? Is there no common
content ?
Are you planning to use 1 server for varnish ? How bad is it for
business when it crashes ?
Regards,
Martin
Davies Matt J A (LCSS) wrote:
Hello everyone
What is the best practice way of setting up varnish to act as a cache for more
than one web site?
I can see I can make multiple backend, and I've read that I can run multiple
instances of varnish, I'm just wondering what is the best practice way?
One thing I can't quite get my head around is how do I tell varnish which
incoming URL to serve with which backend, or instance.
Scenario
I've got our DNS boys to point a.com and b.com at our varnish server, which is
going to act as a cache for both sites, both sites being very different and
needing different rules. Rules that may collide also.
If I use the multiple instance route, how do associate an instance with an
incoming URL?
Also, the same applies for multiple backends in the same instance.
I'm brand new to Varnish so this is probably a remarkably stupid question,
apologies for my greeness.
Matt
_______________________________________________
varnish-misc mailing list
[email protected]
http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
_______________________________________________
varnish-misc mailing list
[email protected]
http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
