websocketd
inlets-archived
Our great sponsors
websocketd | inlets-archived | |
---|---|---|
14 | 8 | |
17,085 | 8,407 | |
- | - | |
0.0 | 8.0 | |
6 months ago | almost 3 years ago | |
Go | Go | |
BSD 2-clause "Simplified" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
websocketd
- Ask HN: Tips to get started on my own server
-
Pipexec – Handling pipe of commands like a single command
Somewhat related: https://github.com/joewalnes/websocketd
> websocketd is a small command-line tool that will wrap an existing command-line interface program, and allow it to be accessed via a WebSocket.
-
Structured Logging with Slog
I hadn't even considered collecting traces/spans in this way yet, and have taken the approach of "stuff outputting logs in JSON format to stderr/local file". I usually end up writing a (temporary, structured) log message with the relevant span tags, but wouldn't it would be much better to run the actual trace/span code and be able to verify it locally without the ad-hoc log message?
The prototype I built is a web application that creates websocket connections, and if those connections receive messages that are JSON, log lines are added. Columns are built dynamically as log messages arrive, and then you can pick which columns to render in the table. If you're curious here's the code, including a screenshot: https://github.com/corytheboyd-smartsheet/json-log-explorer
With websockets, it's very easy to use websocketd (http://websocketd.com), which will watch input files for new lines, and write them verbatim as websocket messages to listeners (the web app).
To make the idea real, would want to figure out how to not require the user to run websocketd out of band, but watching good ol' files is dead simple, and very easy to add to most code (add a new log sink, use existing log file, etc.)
-
Ask HN: WebSocket server transforming channel subscriptions to gRPC streams
* Additionally, client can stream data to the backend server (if bidirectional GRPC streams are used). I.e. client sends WebSocket messages, those will be transformed to GRPC messages by WebSocket server and delivered to the application backend.
As a result we have a system which allows to quickly create individual streams by using strict GRPC contract but terminating connections over WebSocket transport. So it works well in web browsers. After that no need to write WebSocket protocol, client implementation, handle WebSocket connection. This all will be solved by a suggested WebSocket server and its client SDKs.
The mechanics is similar to Websocketd (https://github.com/joewalnes/websocketd), but instead of creating OS processes we create GRPC streams. The difference from grpc-web (https://github.com/grpc/grpc-web) is that we provide streaming capabilities but not exposing GRPC contract to the client - just allowing to stream any data as payload (both binary and text) with some wrappers from our client SDKs side for managing subscriptions. I.e. it's not native GRPC streams on the client side - we expose just Connection/Subscription object to stream in both directions. GRPC streams used only for communication between WebSocket server and backend. To mention - grpc-web does not support all kinds of streaming now (https://github.com/grpc/grpc-web#streaming-support) while proposed solution can. This all should provide a cross-platform way to quickly write streaming apps due to client SDKs and language-agnostic nature of GRPC.
I personally see both pros and cons in this scheme (without concentrating on both too much here to keep the question short). I spent some time thinking about this myself, already have some working prototypes – but turned out need more opinions before moving forward with the idea and releasing this, kinda lost in doubts.
My main question - whether this seems interesting for someone here? Do you find this useful and see practical value?
-
WebSocket to TCP bridge for game servers? Alternative to websockify?
I also used to use this (http://websocketd.com/) along with netcat(1) before just biting the bullet and writing my own websocket library for our server as we needed to scale up slightly.
-
A library for exposing simple scripts? (Scripts As A Service)
Another option if you’re ready to implement the frontend part is https://github.com/joewalnes/websocketd which has the advantage of streaming the output of your script
- websocketd
-
Show HN: How did I live without Pipe Watch?
Wanted to add websocketd [1]. It's an amazing tool to stream debugging logs to another system where you can build your webapps that accumulate alerts.
Use it only for debugging builds and not for production (obviously).
[1] https://github.com/joewalnes/websocketd
- Websocketd – It's like CGI, twenty years later, for WebSockets
inlets-archived
-
Is it normal for an open source creator to be angry you used their code because they "revoked" it?
This appears to be a very old version of the project before it was eventually forked to a repo that belonged to the inlets org on GitHub. That's why when Alex deleted the github.com/inlets/inlets-archived repo yesterday (a fork he controlled, where all the work since late 2018 was done), this repo under the-cc-dev now appears as the root repo of all the forks that exist right now, including my fork (https://github.com/mattwelke/inlets-archived).
-
are there any open source microservice projects for a home user?
Also if you're looking to self host something checkout inlets: https://docs.inlets.dev/#/
-
No port forwarding and bad VPNs - cheap, reliable alternative?
I've used Hamachi (vpn.net), that worked pretty well. You could also try Inlets (https://github.com/inlets/inlets).
-
port-forwarding behind a firewall
Did you check https://github.com/inlets/inlets ? It’s an opensource alternative to cloudfared. Never use it myself but creator has a good track-record of developing nice oss solutions (were raspberry is usually first-class citizen)
-
Which method do you prefer for accessing your Kubernetes API Server within the Private Network?
I found some of them that are related to this topic, it might be useful for you too: * inlets * kt-connect * shuttle * ngrook
- Ngrok alternative (TCP for the most part) for remote SSH
- Show HN: Inlets 3.0 RC1
-
Azure Hybrid Connection Manager Latency
You could build something similar to HCM yourself. For instance you can use Inlets but you'd have to maintain the server yourself and pay for it. Plus, HCM is a breeze to set up and can be automated with the Azure CLI
What are some alternatives?
websocat - Command-line client for WebSockets, like netcat (or curl) for ws:// with advanced socat-like functions
chisel - A fast TCP/UDP tunnel over HTTP
Crow - A Fast and Easy to use microframework for the web.
kt-connect - A toolkit for Integrating with your kubernetes dev environment more efficiently
quickserv - Dangerously user-friendly web server for quick prototyping and hackathons
Nebula - A scalable overlay networking tool with a focus on performance, simplicity and security
ArduinoWebsockets - A library for writing modern websockets applications with Arduino (ESP8266 and ESP32)
localtunnel - expose yourself
IncludeOS - A minimal, resource efficient unikernel for cloud services
sshuttle - Transparent proxy server that works as a poor man's VPN. Forwards over ssh. Doesn't require admin. Works with Linux and MacOS. Supports DNS tunneling.
sish - HTTP(S)/WS(S)/TCP Tunnels to localhost using only SSH.
inlets - Expose your local endpoints to the Internet