Dashboard Service
Dashboard Service is a demo service for a HashiCorp Consul class that fetches a number from a backend counting service.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
51/100 Fair
- Maintained
- No data
- Popular
- No data
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 85512 MB minimum RAM
Based on 2 of 4 factors.
No GitHub repository data collected yet.
Resources & Compatibility
Minimum requirements: 512 MB RAM. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Create and edit your .env file first Run `cp .env.example .env` to create the settings file, then set `NEXT_PUBLIC_E2B_DOMAIN` to the address of the E2B backend the dashboard should talk to. Without it, the dashboard won’t know where to connect and E2B calls can fail. source
- Add your E2B API key to .env If you’re self-hosting, put a valid `E2B_API_KEY` in `.env` and keep that file private. A missing or wrong key can block dashboard actions, while a leaked key can let others use your E2B account. source
- Install and start with Bun Run `bun install` to download dependencies, then `bun run build` and `bun run start` to launch the app. Skipping install can stop the build or startup because required packages are missing. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I point the dashboard at the right backend before first launch?
Copy .env.example to .env and set NEXT_PUBLIC_E2B_DOMAIN to the backend address; without it the dashboard won't know where to connect and E2B calls can fail.
What credential must I provide when self-hosting the dashboard?
Put a valid E2B_API_KEY in .env and keep that file private; a missing or wrong key can block dashboard actions.
Where should I post questions, comments, or bug reports for the Cloud Dashboard Service project?
Use the Cloud Dashboard Service discussion thread, which is intended for questions, comments, bug reports, and other relevant project information.
Answers sourced from forums.ni.com, github.com, github.com
Community
- An effective dashboard for Service Desk and Customer Support teams in ... (other)
- NI Cloud Dashboard Service Discussion - NI Community (forum)
Collected 48 days ago - public community threads