Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By richard102 on
Apologies for asking an 'old' question, but I cannot find the information I remember reading ages ago.
I want to setup a second site (a second internet URL - not a subsite) to be serviced by my current blog-site hardware.
At a very high level - I understand DynDns translates between my URL and my IP address (changable). Then my home-router forwards these requests (on port 80) to my web-server.
On this server I have a wamp stack (from bitnami). Therefore the easiest 'second-site' set-up for me would be to install a completely seperate second stack (with othing shared), where I guess, a second install of Apache would detect the first install and insist on a distinct port number (81?).
(this is where my brain gets a bit ... wooley :-))
Does DynDns distinguish between the two URL's? or does my home-router send URL-1 to server-1 and URL-2 to ... er ... server-1.
Or do I need a common apache install, so traffic for both URL's are not seperated until Apache seperates them?
any help gratefully received :-/
Comments
Way overcomplicated
You're overcomplicating things. Don't run multiple instances of Apache.
Apache supports name-based virtual hosts, which means multiple websites running on exactly the same hardware and exactly the same webserver software, but with different htdocs directories. In this very common scenario, you would install multiple copies of Drupal, presumably pointing at multiple databases.
But even better, Drupal supports multiple websites delivered automatically from the same htdocs directory. In this scenario, you tell Apache to deliver both domains from the same directory and Drupal figures out which settings.php file to read. This is called multisite hosting, and is thoroughly explained in the documentation.