mercury-web-dashboard-deploy

Deploys and maintains the Mercury Web Dashboard service on port 8080 with Tailscale peer discovery and health monitoring.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill mercury-web-dashboard-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mercury-web-dashboard-deploy
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/devops/mercury-web-dashboard-deploy
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill mercury-web-dashboard-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you deploy, troubleshoot, and keep the Mercury Web Dashboard running reliably without manual guesswork.

Core Features & Use Cases

  • Dashboard Deployment: Start the aiohttp-based Mercury Web Dashboard on port 8080 with the expected frontend, API, and WebSocket endpoints.
  • Operational Recovery: Resolve common runtime issues such as port conflicts, silent process exits, and incomplete peer enrichment.
  • Tailscale Peer Discovery: Support userspace-networking Tailscale setups, socket-aware status checks, and peer visibility fixes for the dashboard.
  • Use Case: A developer notices the dashboard is down or peers are missing, and uses this Skill to restart the service, free the port, and restore discovery health.

Quick Start

Ask the skill to deploy the Mercury Web Dashboard and apply the documented port, Tailscale, and health-check recovery steps.

Frequently Asked Questions about mercury-web-dashboard-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy the Mercury Web Dashboard on aiohttp?

To deploy the Mercury Web Dashboard, start the aiohttp service on port 8080 to host the frontend, API, and WebSocket endpoints, then apply documented health-check recovery steps to ensure continuous availability monitoring.

Why does the Mercury dashboard lose Tailscale peer visibility?

Tailscale peer visibility drops when userspace-networking setups fail socket-aware status checks or peer enrichment. Restore discovery health by applying peer-enrichment fallbacks and socket-aware status checks to bridge the WebSocket peers.

What is the best way to recover port 8080 for the Mercury dashboard?

The best way to recover port 8080 is to resolve the port conflict and handle silent process exits through resilient restart handling, freeing the port for the aiohttp dashboard service to resume hosting.

Does the Mercury dashboard support auto-health-cron supervision?

Yes, the Mercury dashboard supports auto-health-cron supervision to maintain continuous availability. This mechanism monitors the service and triggers resilient restart handling to prevent unexpected downtime.

How do WebSocket peer bridges work in the Mercury Web Dashboard?

WebSocket peer bridging connects dashboard peers by routing real-time updates through the aiohttp server. Tailscale-based peer discovery populates the peer list, with fallbacks enriching incomplete peer data when discovery fails.

Can I use Tailscale userspace networking to host the Mercury dashboard?

Yes, you can use Tailscale userspace networking to host the Mercury dashboard. The deployment supports Tailscale-based peer discovery, socket-aware status checks, and peer visibility fixes specifically designed for userspace setups.