Troy McConaghy 5403f7bfcc Remove "Post-Release Steps" from release process (#2305)
The release process had some "Post-Release Steps" but I haven't been doing them lately. What were they?

The idea was to change the version number so that someone working on the `master` branch would see a version number reflecting what the `master` branch is. For example, if version 0.9.0 was just released, then the `master` branch would be changed to have the version number 0.10.0.dev, to indicate that it's the in-development version of 0.10.0.

My thinking now is that if someone is developing new code, then they don't need the version number to help them remember what they're doing. Moreover, if someone purposefully changes the docs to view the `master` branch docs, then they probably know what that means, and they don't need help from a version number.
2018-05-18 11:26:37 +02:00
2018-02-08 15:41:44 +01:00
2017-01-11 05:13:27 -05:00

PyPI PyPI Travis branch Codecov branch Documentation Status Join the chat at https://gitter.im/bigchaindb/bigchaindb

BigchainDB Server

BigchainDB is a blockchain database.

Run and test BigchainDB from the master branch

Running and testing the latest version of BigchainDB is easy. Make sure you have a recent version of Docker Compose installed in your host.

Whenever you are ready, fire up a terminal and run:

git clone https://github.com/bigchaindb/bigchaindb.git
cd bigchaindb
make run

BigchainDB should be reachable now on http://localhost:9984/.

There are also other commands you can execute:

  • make start: Run BigchainDB from source and daemonize it (stop it with make stop).
  • make stop: Stop BigchainDB.
  • make logs: Attach to the logs.
  • make test: Run all unit and acceptance tests.
  • make test-unit-watch: Run all tests and wait. Every time you change code, tests will be run again.
  • make cov: Check code coverage and open the result in the browser.
  • make doc: Generate HTML documentation and open it in the browser.
  • make clean: Remove all build, test, coverage and Python artifacts.
  • make reset: Stop and REMOVE all containers. WARNING: you will LOSE all data stored in BigchainDB.

To view all commands available, run make.

Get Started with BigchainDB Server

Quickstart

Set Up & Run a Dev/Test Node

Run BigchainDB Server with Docker

Run BigchainDB Server with Vagrant

Run BigchainDB Server with Ansible

Description
Meet BigchainDB. The blockchain database.
Readme 15 MiB
Languages
Python 83.6%
Shell 12.5%
Lua 1.6%
Dockerfile 0.8%
Jinja 0.7%
Other 0.8%