Web Console

Provides a simple web interface for command-line applications - quickly publish a Python / Bash / Powershell / Batch / etc script as a basic web app. Turns STDOUT into formatted text, alerts and progress indicators.

Cross-platform, runs as a self-contained web server, binaries are available for Windows and Linux (including Raspberry Pi). The install process includes setup as a service on each platform.

Web Console is intended to be used behind a proxy server or tunneling service, it doesn’t by itself handle HTTPS connections. Web Console has been used behind Apache and NGINX acting as reverse-proxy servers, we recommend Caddy for its ease-of-use in automatically dealing with HTTPS provision for you. Web Console includes built-in support for tunnling-with-authentication services from Cloudflare and ngrok.

Web Console’s implementation prioritises ease of configuration and use - it’s easy to manipulate configurations and user data to provide the functionality you want.

As well as providing a user interface, Web Console also provides a simple REST API, providing URLs for services such as IFTTT and Zapier or letting you trigger tasks from remote systems (including GitHub Actions) with command-line tools like wget and curl.

If the above explanation of what Web Console is doesn’t match up with what you are trying to do, try the Alternatives page for links to applications that might be more suitable.

Live Demo

You can use a working live demo right now, or simply watch this quick (30-second) video:

Demo of Web Console

The above link runs a simple demo application that produces some example output, showing the different types of output message supported. It also prints a progress percentage, which is displayed by Web Console as a progress bar.


Installation instructions for all platforms, including details of building from source, can be found on the installation page.


Web Console runs “tasks”, individual scripts / applications that each have their own URL where execution can be triggered and output can be seen. Pretty much any existing application runable from the command line should work, returning any console output sent to STDOUT or STDERR to the web-based user interface.

If you are writing a new script or command line utility (or reformatting the output from an existing utility) you can produce output specifically for Web Console to interpret and display in certain ways. For more details, see the Tasks documentation page.

The Webconsole binary is also used as a command-line tool for configuration. At the command line, type webconsole --help for a command summary.


If you install Web Console using the install script then it should run as a service, starting when your machine boots. If you just run the binary, without any other arguments, it will start and listen (by default) on port 8090 for HTTP connections. If you start with the “debug” argument, i.e.:

webconsole --debug

Then Web Console will start in debug mode, printing information to the console about each received HTTP request.

Main Configuration

On startup, Web Console attempts to locate a configuration file. This can be in CSV or Excel format, named “config.csv” or “config.xlsx”. It will first look in /etc/webconsole on MacOS / Linux, or in C:\Program Files\webconsole on Windows, followed by the current folder.

The configuration file has a simple Parameter, Value format. Valid parameters are:

Task Configuration

Webconsole will look in the defined “tasks” folder (by default, on Linux / MacOS, /etc/webconsole/tasks, on Windows, C:\Program Files\webconsole\tasks) for subfolders. Any subfolders found will be searched for a “config.txt” file and used as a Task ID if found. Task IDs generated by the Webconsole application are random 16-character strings, but any string (no spaces) can be used.

The format of config.txt is a basic YAML-style text - keywords followed by a colon then the given value, e.g.:

title: Test Site
public: N
command: /root/buildSite.sh

Valid keywords are:

Note that changes to config.txt for any Task will be in effect the next time the Task is triggered, without any need to restart / reload anything server side or even refresh the web interface if you already have the Task’s page open.

More details can be found on the documentation page.


This project contains binaries from The Non-Sucking Service Manager by Iain Patterson, used to set up services on Windows. Public Domain license.

The web user interface is constructed using Bootstrap 5 with Popper.

In-browser Markdown rendering (for the “description” section of each Task page) is handled by the Marked Javascript library.

The text editor in the “Edit” section of the user interface is implemented using Ace.

All required Javascript library files are included in the release distributions so Web Console can run as a self-contained application on a non-networked workstation / kiosk device if needed. Note that Ace isn’t embedded in the project in the same way the other Javascript libaries are (the Ace project consists of a large number of separate JS files, and I couldn’t figure out Git’s sub-project feature…), it’s simply copied into the www/ace folder at build time - check the build scripts (build.sh/build.bat) for details.

Code for the resizeable file browser / code editor panel originated from Nguyen Huu Phuoc.

Code for the file browser tree view originated from W3Schools.

To Do / Roadmap

See the dedicated To-Do list in the documentation.