A control panel that lets you monitor and control your ComputerCraft and/or ComputerCraft: Tweaked turtles through a WebSocket connection.

The turtles show up on the dashboard where their online status, activities and fuel consumption can be easily monitored.

Clicking on a specific turtle brings you to that turtle's control panel where you can monitor it, change its current activity, manipulate its inventory or simply watch it move around in the world.

The 3D map only shows you what the turtle can see (or have seen) and may not be a realistic interpretation of the world as it may have changed since the last time the turtle inspected the blocks. It is highly recommended to use this control panel along with at least one of the supported mods for rapid world discovery:

• Advanced Peripherals by utilizing the Geo Scanner peripheral.
• Plethora by utilizing the Block Scanner peripheral.
• UnlimitedPeripheralWorks by utilizing the Universal Scanner peripheral.

Setup

Before you begin make sure that Node.js is installed, then clone the project with git clone and make sure your working directory is within the cloned project.

Environment variables (all optional)

• TURTLE_WSS_PORT - Port for the second WebSocket server used by the turtles (defaults to 5757)
• LOG_LEVEL - Log level for the server (defaults to info). Possible values are: emerg, alert, crit, error, warning, notice, info, debug
• TURTLE_LOG_LEVEL - Log level for the connected turtles (defaults to INFO). Possible values are ERROR, WARNING, INFO, DEBUG

Portal

# Change the working directory
cd portal

# Install dependencies
npm install

# Build the portal
npm run build

# Start the portal
npm run start

After starting the server up you can go to http://localhost:3000 to check it out, but keep in mind there won't be much here until we connect the first turtle.

Turtle

Run the following command inside your turtle:

> wget run https://raw.githubusercontent.com/runi95/turtle-control-panel/master/turtle/downloader.lua

NOTE: If you're not on a local server running as localhost then make sure to edit the connectionURL variable in startup.lua (on the turtle) to your own IP address (or server URL). If you're on a local server then this step can be skipped.

> edit startup.lua

NOTE: If you want to run this on a local server running as localhost then check out this CC:Tweaked guide on Allowing access to local IPs before you reboot the turtle or the connection will fail.

> reboot