🤝 Web interface (Toxihub) 🙊
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
Hi Shopify team! 👋
First off, thank you for creating Toxiproxy - it's been an invaluable tool for our chaos engineering practices over the past few months.
While using Toxiproxy, we encountered a common challenge: managing numerous proxies and toxics exclusively through CLI became increasingly complex as our testing scenarios grew. To address this, we developed Toxihub - a web-based interface that complements Toxiproxy's native REST API.
What is Toxihub?
Toxihub is a Node.js wrapper that provides:
- 🖥️ An intuitive web UI for managing proxies and toxics
- 🔧 Simplified REST API endpoints for common operations
- 📊 Real-time visualization of active proxies and their toxics
- ⚡ One-click operations (start/stop server, toggle proxies, inject toxics)
- 🎨 A terminal-themed interface that feels familiar to DevOps engineers
Repository: https://github.com/videsk/toxihub
Web interface: https://toxihub.videsk.io/
Key Features
- Zero Configuration: Works with existing Toxiproxy installations
- Auto-discovery: Automatically detects and syncs with running Toxiproxy instances
- Simplified Toxic Management: Visual forms for configuring latency, bandwidth, timeouts, etc.
- Bulk Operations: Easily reset all proxies or apply common network conditions
- Cross-platform: Runs on any system where Node.js is available
Community Collaboration
We built Toxihub to solve our own challenges, but we believe it could benefit the wider Toxiproxy community. We're actively seeking feedback to improve and enhance the tool based on real-world usage patterns.
Would love to hear your thoughts and suggestions! We're committed to maintaining this as an open-source companion tool to Toxiproxy.
Thank you for your time and for creating such an amazing tool! 🚀
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Toxihub repository and live interface linked in the issue to understand the proposed companion tool. No file, test, or concrete change is specified; a contribution would need a maintainer decision about whether or how it should be integrated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, node.js
- Domain
- tooling, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100