Hello,
Apache2.4 can be configured with IP-based, or Name-based VirtualHost's.
Apache2.4 can handle multiple of such.
But You need to point the Domain.TopLevelDomain to a IP, if You choose
the first plan.
On the second plan, You need to extend configure the Apache2.4 with
DocumentRoot, ServerName
Surely it will, but in practice, with shared hosting, you'd assign a single
vhost to each customer.
This is where Alias / AliasMatch comes into play.
On Mon, 4 Apr 2022 at 11:35, Jim Albert wrote:
> On 4/4/2022 11:16 AM, Eric Covener wrote:
> > On Mon, Apr 4, 2022 at 11:11 AM A wrote:
> >> Hi,
On 4/4/2022 11:16 AM, Eric Covener wrote:
On Mon, Apr 4, 2022 at 11:11 AM A wrote:
Hi,
I am planning to make changes to Apache web server so that it can serve
multiple websites (not sub-domains) from port 80.
This will save money for someone who has more than one website. That person
need n
Sounds like simple Alias directives in the main vhost should suffice.
On Mon, 4 Apr 2022 at 11:17, Eric Covener wrote:
> On Mon, Apr 4, 2022 at 11:11 AM A wrote:
> >
> > Hi,
> >
> > I am planning to make changes to Apache web server so that it can serve
> multiple websites (not sub-domains) fro
On Mon, Apr 4, 2022 at 11:11 AM A wrote:
>
> Hi,
>
> I am planning to make changes to Apache web server so that it can serve
> multiple websites (not sub-domains) from port 80.
>
> This will save money for someone who has more than one website. That person
> need not buy more than one hosting pl
