Use Apache2's Name-based virtual host
to run multiple websites on the same server.
Note that if you are using databases to drive your website such as for content management, you still need to decide if the development and production sites use the same database or the development database is copy that you can safely break during testing.
For DNS the optimum approach is to populate whatever your local network uses for DNS with a CNAME for each website so that the development and live sites both resolve to the dedicated server's A record (and IP).
Your router might be able to do this, or Windows Server can run DNS service.
Failing that you can otherwise distribute these entries to the hosts files on each computer.
I mean, it's ok for the sake of a few computers but doesn't scale well and inconvenient if you'd like to check how well your web page layouts adapt on a tablet or smartphone.
For editing the web pages on the server using client software on the laptop:
* For client OSes other than Windows, folders on a server can be mounted by as SFTP paths and any editing software can work directly on the files as if local
* for the sake of Windows clients you can expose the folder containing your websites as a Windows File Share if it is only accessed from the local network
prlzx on iDNET: FTTC (VDSL) at ~40Mbps / 10Mbps
with IP4/6 (no v6? - not true Internet)
Edited by prlzx (Fri 19-Jun-20 12:17:31)