https://github.com/etherdata-blockchain/etd-local-admin-node
Admin Node
https://github.com/etherdata-blockchain/etd-local-admin-node
Last synced: 4 months ago
JSON representation
Admin Node
- Host: GitHub
- URL: https://github.com/etherdata-blockchain/etd-local-admin-node
- Owner: etherdata-blockchain
- Created: 2021-07-25T04:29:03.000Z (almost 5 years ago)
- Default Branch: main
- Last Pushed: 2026-01-20T01:24:57.000Z (5 months ago)
- Last Synced: 2026-01-20T08:44:47.453Z (5 months ago)
- Language: TypeScript
- Homepage:
- Size: 4.41 MB
- Stars: 0
- Watchers: 0
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: readme.md
- Changelog: CHANGELOG.md
Awesome Lists containing this project
README
# ETDAdmin Node
[](https://codecov.io/gh/etherdata-blockchain/etd-local-admin-node)
[](https://github.com/etherdata-blockchain/etd-local-admin-node/actions/workflows/build-stable-image.yml)
[](https://www.codacy.com/gh/etherdata-blockchain/etd-local-admin-node/dashboard?utm_source=github.com&utm_medium=referral&utm_content=etherdata-blockchain/etd-local-admin-node&utm_campaign=Badge_Grade)
## Run
1. Install dependencies
```
yarn install
```
2. Build
```
yarn build
```
3. Start
```
node dist/app.js
```
## Available environments
rpc=
wsRpc=
db=
etd_node_id=
etd_node_name=
NODE_ENV=development
## Development
This project was split into following design pattern.
1. Handler - When remote sends any command or any schedule jobs triggered, handler will be called.
2. Service - When handler received jobs, it will be sent to the corresponding service to handle.
3. Remote client - Handle every connection between client and server
In general, services are contained by handler, and handler will decide how to use its services.