https://github.com/stultuss/node-ws-server
Distributed Message Service Cluster for Service Registration and Discovery via ETCD
https://github.com/stultuss/node-ws-server
distributed-systems nodejs service-registration-discovery typescript websocket
Last synced: 3 months ago
JSON representation
Distributed Message Service Cluster for Service Registration and Discovery via ETCD
- Host: GitHub
- URL: https://github.com/stultuss/node-ws-server
- Owner: stultuss
- License: mit
- Created: 2019-11-05T14:04:18.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2022-12-10T07:57:44.000Z (over 2 years ago)
- Last Synced: 2025-01-22T13:51:40.882Z (5 months ago)
- Topics: distributed-systems, nodejs, service-registration-discovery, typescript, websocket
- Language: JavaScript
- Homepage:
- Size: 10.1 MB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
im-server
==========================
> Distributed Message Service Cluster for Service Registration and Discovery via ETCD
## Aim
This project is to provide a reliable message service，By making this project into a docker image, you can quickly build a distributed message service cluster on the docker container platform.
You can also customize your message service cluster by modifying the code.
## How to use
* Generate discovery url
```bash
curl -s http://discovery.etcd.io/new?size=3
// https://discovery.etcd.io/9c7d8d23b7d883e5a3348ae66fc85ec7
```
* Modify `start.sh` to replace the discovery url
``` bash
nohup /tmp/etcd/etcd \
-name proxy \
-proxy on \
-listen-client-urls http://0.0.0.0:2370 \
-discovery https://discovery.etcd.io/9c7d8d23b7d883e5a3348ae66fc85ec7 >> /tmp/etcd/output.log 2>&1 & echo $! > run.pid
node ./build/index.js
```
* Build and launch the docker container
``` bash
docker build -t im-server:latest .
docker run -d -p 8080:8080 im-server
```
## Client authentication mode
1. default
> To allow any client access, the Token required to connect to the server must be generated in conjunction with `secret.user` in the server configuration.
2. strict
> Allow only token authenticated client access。
## Token generating rule
``` typescript
const token = md5(“${secretKey}_${uid},${ipAddress},${loginTime}”).substr(0, 8)
```