Varnish on stand-alone server
Miguel González
miguel_3_gonzalez at yahoo.es
Thu Jan 19 23:26:07 CET 2017
You can use local dns or trick your system using hosts file to have your
own local domain.
On 01/19/17 10:32 PM, Stalker, Tim wrote:
> It would seem that if running varnish on its own server, the backend
> host must point to a fqdn.
>
> ------------------------------------------------------------------------
> *From:* Stalker, Tim
> *Sent:* Wednesday, January 18, 2017 11:28:45 PM
> *To:* varnish-misc at varnish-cache.org
> *Subject:* Varnish on stand-alone server
>
>
> I'm setting up a web development cluster with 3 or 4 backend webservers.
> Because this is all offline at the moment, provisioning this with
> vagrant and ansible in a private network of servers with no fqdn. I have
> no problem getting varnish to connect to the backends over port 80
> from within the varnish VM itself over lynx and curl, but from outside
> the VM on my host machine, varnish is unaware of the backends. Varnish
> works fine if I install it on the same machine as apache but if I try to
> run it in its own virtual machine. I would like to simulate a production
> environment as much as possible when all of the server names are fully
> qualified.
>
>
> Can anyone suggest ways I might get varnish to provide caching from
> browsers on my host machine while running in its own virtual machine in
> a cluster?
>
>
> Thanks a ton
>
>
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
More information about the varnish-misc
mailing list