basecamp / basecamp/thruster

Feature request - allow protocol plugins

Open
#82 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
1.2k
Forks
58
Avg merge
1d 2h
Merged PRs (30d)
6

Description

In some cases I have wanted my application to support multiple protocols
eg: CoAP and MQTT plain TCP etc
It would be great is I could easily add a plugin that supported proxying of the protocols
either into the existing thruster instance, or into a separate instance for each protocol
This way the applications when upgrades to rails 8 can take advantage of the existing rails standard configuration and infrastructure

right now I am forking thruster - removing http(s) and adding my own protocols, and running a separate instance
ie: truster , thruster-coap, thruster-mqtt

This would make deploying in more complex environments easier and remove the need to add additional proxies such as traffic, nginx etc

Contributor guide

Open the contributing guide

Research direction

Start by reading the Thruster codebase and the existing HTTP(S) proxying path; the issue does not name specific files or tests. Compare the current forked setup with separate thruster, thruster-coap, and thruster-mqtt instances. Done would mean a reviewed design and implementation that supports protocol plugins in the existing or separate instances without requiring additional proxies.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.