Digger Webserver App

Digger is a web application. When you run Digger, it starts a local web server, then opens the web app in your browser. It works like a local application, but you can also run the Digger server on one computer and open the web interface from another browser on the same LAN.

Running as server/webapp combination means that Digger on the web is literally the same interface as Digger on your computer. And the local server code is the same across all platforms. That's all great, but you might run into some warning messages depending on your operating system. Here are some things you might see:

Warning about running a free app you downloaded directly:

Operating systems like MacOS, Windows and others prefer you run applications purchased through their stores, which they have some control over. When you run Digger, you might get a warning that it was downloaded directly from the internet. If you are not already familiar with how to tell your computer to go ahead and open it anyway, you might have to look up how to do that. Instructions vary depending on the OS and version, but there is always a way.

The warning serves a purpose, which is to tell you to make sure you trust the program you are about to run. Only download Digger from DiggerHub.com, or install node.js and download the source code from GitHub.

Personal firewall warning:

Because Digger runs as a web server, you might get a firewall notice about whether the service should be accessible to other computers on the same LAN. Serving your home LAN is probably fine, serving everyone in a public coffee shop WiFi is probably not. If you are not sure, go with the default firewall allowances.

Can't run from temp folder:

You might need to move the Digger app from your downloads folder to your desktop or somewhere else you can easily find it and run it again later.

Browser doesn't start:

After the Digger server starts, it spawns a call to open Digger in your default browser. If that didn't come up, the command to open the browser page didn't work. Look for the server console window, and open the URL from the last line.

If you know the command that should have been used to open a URL on your system, and would like to help improve Digger, open a GitHub issue and include

  1. The command that should have been used
  2. Your operating system version
  3. The errors from the server console window

Anything else:

If you run into any other problems running Digger add an issue so the project can try fix it.