Mercury vhosts (name based) only available on port 8080

Hi,

I found this same issue.
I changed the VHOST from binding to my IP to binding to all available IP's.
Here is what I now have and it works as expected. I then add some firewall rules to block out the high port from the outside world.

NameVirtualHost *:9880

<VirtualHost *:9880>
.......
</VirtualHost>   

The next thing is the sites you have with drupal and not pressflow are not going to work on port 80 (varnish).
As long as you haven't modified the drupal core you should be able to easily move the sites to pressflow.

Varnish will pass the request to Apache if it is unable to serve from cache. So your core Drupal sites should work fine.

Thank's @aaron01. I didn't realise Drupal would still work with varnish, just not accelerated in any way.

I probably will never need this as a site just works with Pressflow without any need of migrating (as long as the core has not been tampered with)

So, let me get this straight.

1) You can setup Mercury/Pressflow with a VPS (Pantheon Mercury Linode stackscript), and use name based virtual hosts to serve both Pressflow and standard Drupal core sites off standard port 80?

2) You could - Move your Drupal standard core site to a Mercury/Pressflow site, and then "down-grade" or "standardize" it again if the need arises relatively simply - IE just changing the Drupal core files from Pressflow to standard Drupal core? No changing of the DB needed?

3) This would apply to any simple HTMl or say Wordpress sites you had in your Apache file as well ("Varnish will pass the request to Apache if it is unable to serve from cache.")?

Thanks.

I'm serving two Drupal core sites and one Pressflow site with vhosts on Mercury and it's been working great. My question is, can I use the multi-site Mercury instructions to convert all my sites over to Mercury configured Pressflow (Varnish, Solr, Memcached) on Mercury 1.0, or do I have to upgrade to 1.1 first?