Displaying a bunch of html files in your own local web server is easier than it sounds. The package manager npm for the web application framework Node.js comes with a zero-configuration http server that can be started within seconds without.
Installing npm and Node.JS
If you haven’t done so yet, install the node package manager npm which is a Node.JS application.
Mac OS X
Normally the the best way is to use the official installer for Node.JS. The packager manager npm is included in the installer.
If you have installed Mac Ports it is probably better to install the port instead:
Or with homebrew you do:
Use the official installer for Node.JS!
Either npm or Node.JS will be available as a package for your distribution. If there is a separate package for npm, then install that, because it will install Node.JS as a dependency. Otherwise just install Node.JS which will contain npm. The package name of Node.JS will be “nodejs” or just “node”, depending on your distribution.
Running the Ad Hoc Web Server
Installing the HTTP Server
The http server is a Node.JS package
http-server and will be installed
via the command line:
Windows users omit the “sudo” here.
Starting the HTTP Server
Now change to the directory that contains your html files and start the server:
-o will start your default browser automatically. You will either
see a listing of files or a web page if the directory contains a file
If you want to see everything in a different browser point it to the address http://127.0.0.1:8080/.
Stopping the Server
If you want to stop the server either close the command-line window or hit
Ctrl-C when it is in the foreground.
Starting Multiple Servers
Start a second http server in parallel will not work because the address is already in use. In that case you can start the server on a different port number, for example 8081:
If port 8081 is also in use try a random number between 1024 and 65535 until you find a free port.
Browsing On Mobile Devices
If you configure your firewall accordingly, you can also browse your ad-hoc site on mobile devices. When you start a server, the list of available addresses is printed out:
The first IP
127.0.0.1 is always the same and only reachable from your own
computer. All other IPs can be accessed from within your network.
If you are too lazy typing the address into your mobile browser, you can
use QR codes. Copy the address with
CTRL-C into the clipboard, go to
one of the many online QR code
generators, paste the address with
CTRL-V and scan the QR code with
a QR code scanner app.
Watching Changes With Browsersync
It is even possible to make the browser reload a page as soon as you change one of the files in the directory. If that sounds fun for you go ahead:
Install browser-sync with the command
sudo npm install -g browser-syncor just
npm install -g browser-sync.
Start the web server with
browser-sync start -sand enjoy.
Whenever you modify the displayed file, the page is automatically reloaded. Usually that happens in fractions of a second, so fast that you don’t even notice it. If a ressource in that page changes, for example an image or a stylesheet, the DOM of the page gets updated without a reload and only that particular part is updated.
If you want to enable directory listings add
--directory to the command line
options. And, by the way, you can start as many instances of Browsersync
as you want. It will pick the next free port if its default port 3000 is
The real fun with Browsersync starts, when you point a second or third browser for example on your phone or tablet to your local server. All browsers are synchronized, all mouse clicks, inputs or other user interactions are mirrored across all connected devices.
Synchronizing browsers with Browsersync
And wouldn’t it be cool to present your new company web site instead of
local files and let all people
around you follow while you are clicking, scrolling and sending forms? A piece
of cake with Browsersync:
browser-sync --proxy http://www.yoursite.com. Now
everybody connecting to your local server will see
instead. But be aware that the synching is unidirectional! Everybody
connected can control the browser of everybody else.
By the way, Browsersync comes with tons of other features that can be explored by visiting the address http://127.0.0.1:3001 (or whatever other UI address was printed out in the command-line window).
Of course, you should only experiment with these ad-hoc servers in trusted
networks or after securing them a little.
http-server --help or
browser-sync server --help give instructions for that.
blog comments powered by Disqus