# Deploy Service
# BitalosFE
BitalosFE is the cluster management backend, which mainly includes: node information display (bitalosdashboard, bitalosproxy, bitalostored) and multi-cluster operation and maintenance operations.
Deploying BitalosFE service is the first step to create a cluster. Usually, deoloying BitalosFE service only needs to start one process in development environment, even if multiple clusters are created.
# Sqlite
Local experiments can be started using sqlite. The startup command is:
> nohup bin/bitalosfe --assets-dir=bin/dist --sqlite={SqliteDir}/bitalos-demo.db --log={BitalosFeDir}/fe.log --pidfile={BitalosFeDir}/bitalosfe.pid --log-level=INFO --listen=0.0.0.0:8080 >> /tmp/fe.out 2>&1 &
Options:
- assets, BitalosFE static files (js, css, etc.)
- sqlite, the sqlite database file
- log, log file
- pigfile, pid file
- log-level, log level
- listen, BitalosFE working address
# Mysql
Mysql is required if deployed in production environment. The startup command is:
> nohup bin/bitalosfe --assets-dir=bin/dist --db=database --db-hostport={MysqlIp}:{MysqlPort} --db-username={MysqlUser} --db-password={MyqlPassword} --db-dbname={Database} --log={BitalosFeDir}/stored-fe.log --pidfile={BitalosFeDir}/stored-fe.pid --log-level=INFO --listen=0.0.0.0:8080 >> /tmp/fe.out 2>&1 &
Options (different from sqlite):
- db, "database" means using mysql database
- db-hostport, mysql address
- db-username, mysql auth user
- db-password, mysql auth password
- db-dbname, mysql database name
# Bitalosdashboard
Bitalosdashboard config: bitalosdashboard config
# Sqlite
Local experiments can be started using sqlite. The startup command is:
> nohup bin/bitalosdashboard --config={BitalosDashboardDir}/conf/bitalosdashboard.toml --sqlite={{SqliteDir}}/bitalos-demo.db --log={BitalosDashboardDir}/dashboard.log --log-level=INFO --pidfile={BitalosDashboardDir}/bitalosdashboard.pid > {BitalosDashboardDir}/dashboard.out 2>&1 &
Options:
- config, config file
- sqlite, the sqlite database file, value is same as BitalosFE sqlite value
- log, log file
- log-level, log level
- pigfile, pid file
# Mysql
Mysql is required if deployed in production environment. The startup command is:
> nohup bin/bitalosdashboard --config={BitalosDashboardDir}/conf/bitalosdashboard.toml --database=database --log={BitalosDashboardDir}/dashboard.log --log-level=INFO --pidfile={BitalosDashboardDir}/stored-dashboard.pid > {BitalosDashboardDir}/dashboard.out 2>&1 &
Options (different from sqlite):
- database, "database" means using mysql database
# Bitalosproxy
Bitalosproxy config: bitalosproxy config
The startup command is:
> nohup bin/bitalosproxy --config=conf/bitalosproxy.toml --dashboard=127.0.0.1:8080 --pidfile={BitalosProxyDir}/bitalosproxy.pid >> {BitalosProxyDir}/proxy.out 2>&1 &
Options:
- config, config file
- dashboard, admin address of BitalosFE (domain name or ip:port)
- pidfile, pid file
# Bitalostored
Bitalostored config: bitalostored config
The startup command is:
> nohup bin/bitalostored --conf.file=conf/bitalostored.toml >> {StoredDir}/stored.out 2>&1 &
Options:
- conf.file, config file