Automated Installation

When users would like to automate the process of installing and running HarperDB there is the capability to pass arguments via the command line. Not All arguments are required.
harperdb [ install | run ] --TC_AGREEMENT [yes | no] --HDB_ROOT [PATH] --SERVER_PORT [HTTP/S SERVER PORT] --HDB_ADMIN_USERNAME [USERNAME] --HDB_ADMIN_PASSWORD [PASSWORD] --CLUSTERING_USERNAME [CLUSTERING USERNAME] --CLUSTERING_PASSWORD [CLUSTERING USER PASSWORD] --CLUSTERING_PORT [CLUSTER PORT] --NODE_NAME [CLUSTER NODE NAME] --enable_clustering [TOGGLE FLAG]
ArgumentDefinitionRequired
TC_AGREEMENT[yes|no]: Agree yes, do not Agree no.Yes
HDB_ROOT[PATH]: Full path to where you would like the HarperDB data to be installed. i.e. /tmp/hdbYes
SERVER_PORT[HTTP/S PORT]: Port you would like the HarperDB server to run on. New installations default to HTTP.Yes
HDB_ADMIN_USERNAME[USERNAME]: Username of your administrator user.Yes
HDB_ADMIN_PASSWORD[PASSWORD]: Password for your administrator user.Yes
CLUSTERING_USERNAME[CLUSTERING USERNAME]: Username of your clustering user, needs to be the same between connected nodes.No
CLUSTERING_PASSWORD[CLUSTERING USER PASSWORD]: Password of your clustering user, needs to be the same between connected nodes.No
CLUSTERING_PORTCLUSTERING_PORT]: Port you would like to do clustering communication on.No
NODE_NAME[CLUSTERING NODE NAME]: Cluster node name to reference connected node.No
enable_clustering[TOGGLE FLAG]: No Value needs to be supplied to –enable_clustering it is a flag to enable clustering.No

Here is an example we use internally to automate, build, and test procedures in containers and VMs:
harperdb install --TC_AGREEMENT yes --HDB_ROOT /tmp/hdb --SERVER_PORT 9925 --HDB_ADMIN_USERNAME HDB_ADMIN --HDB_ADMIN_PASSWORD password --CLUSTERING_USERNAME clustering --CLUSTERING_PASSWORD password --CLUSTERING_PORT 1111 --NODE_NAME ci_dev --enable_clustering