| commit | 58617800b7f1384c6c9c87abe8e985ee803293c0 | [log] [tgz] |
|---|---|---|
| author | tison <wander4096@gmail.com> | Tue Oct 31 14:16:25 2023 +0800 |
| committer | GitHub <noreply@github.com> | Tue Oct 31 14:16:25 2023 +0800 |
| tree | 450f2c968e4e1684b418d5fe359a7b1bb68d239d | |
| parent | 15b5ef7dce11dff9afb10824f3b149d87183fd06 [diff] |
refactor!: rename binary to ceresmeta-server (#265) When install the binary with `go install github.com/CeresDB/ceresmeta/cmd/meta@latest`, the result is `meta` which is too general to conflict with other binaries and easily misleading. Rename the binary with a clear long name `ceresmeta-server`. Note that we should adjust ceresdb repo's usage accordingly. If this change gets accepted, I'll handle that. cc @jiacai2050 --------- Signed-off-by: tison <wander4096@gmail.com>
CeresMeta is the meta service for managing the CeresDB cluster.
The project is in a very early stage.
make build
Although CeresMeta is designed to deployed as a cluster with three or more instances, it can also be started standalone:
# ceresmeta0 mkdir /tmp/ceresmeta0 ./ceresmeta --config ./config/example-standalone.toml
Here is an example for starting CeresMeta in cluster mode (three instances) on single machine by using different ports:
# Create directories. mkdir /tmp/ceresmeta0 mkdir /tmp/ceresmeta1 mkdir /tmp/ceresmeta2 # Ceresmeta0 ./ceresmeta --config ./config/exampl-cluster0.toml # Ceresmeta1 ./ceresmeta --config ./config/exampl-cluster1.toml # Ceresmeta2 ./ceresmeta --config ./config/exampl-cluster2.toml
CeresMeta refers to the excellent project pd in design and some module and codes are forked from pd, thanks to the TiKV team.
The project is under rapid development so that any contribution is welcome. Check our Contributing Guide and make your first contribution!
CeresMeta is under Apache License 2.0.