This Github action is creating pre-release version of FoundationDB.
The workflow is building every week:
- the documentation,
- server and client packages,
- Docker images
- Joshua's tests for the bindingtester and correctness target.
DEB | TAR.GZ | Docker | Doc | |
---|---|---|---|---|
Release 7.1 | ✅ | ✅ | ✅ | ✅ |
Artifacts can be found on the latest CI run, or with the Docker release.
# Download both client server targz
$ ls
foundationdb-clients_release-6.3.PRERELEASE.x86_64.tar.gz.zip
foundationdb-server_release-6.3.PRERELEASE.x86_64.tar.gz.zip
# Decompress
$ unzip foundationdb-clients_release-6.3.PRERELEASE.x86_64.tar.gz.zip
$ unzip foundationdb-server_release-6.3.PRERELEASE.x86_64.tar.gz.zip
$ tar -xvf foundationdb-clients*.tar.gz
$ tar -xvf foundationdb-server*.tar.gz
$ rm *.zip *.tar.gz
# Create cluster file
$ echo "local:local@127.0.0.1:4500" > fdb.cluster
# Run fdbserver
$ mkdir {data,logs}
$ ./sbin/fdbserver -p 127.0.0.1:4500 -C $PWD/fdb.cluster -d $PWD/data -L $PWD/logs
# Init database
$ ./bin/fdbcli --exec "configure new single memory"
$ ./bin/fdbcli --exec "status"
$ docker pull ghcr.io/pierrez/foundationdb:7.0.0-prerelease
$ docker run --name fdb --rm -d -p 4500:4500 ghcr.io/pierrez/foundationdb:7.0.0-prerelease
# init database
docker exec fdb fdbcli --exec "configure new single memory"
docker exec fdb fdbcli --exec "status"
You can either:
- change the
LD_LIBRARY_PATH
env var, - use the multi-version client.