Rqlite

- [PR 118](https://github.com/rqlite/rqlite/pull/118): New rqlite CLI. Thanks mkideal
- [PR 125](https://github.com/rqlite/rqlite/pull/125): Add Go runtime details to status endpoint.

- [PR 117](https://github.com/rqlite/rqlite/pull/117): Use Raft advertise address, if exists, during join.

**The Raft log format in 3.0 is not compatible with the 2.0 series**. To upgrade from an earlier version to this release you should backup your 2.0 master node, and replay the database dump into a new 3.0 cluster. The HTTP API remains unchanged however.

- [PR 116](https://github.com/rqlite/rqlite/pull/116): Allow HTTP advertise address to be set.
- [PR 115](https://github.com/rqlite/rqlite/pull/115): Support advertising address different than Raft bind address.
- [PR 113](https://github.com/rqlite/rqlite/pull/113): Switch to in-memory SQLite databases by default.
- [PR 109](https://github.com/rqlite/rqlite/pull/109): Nodes broadcast meta to cluster via Raft.
- [PR 109](https://github.com/rqlite/rqlite/pull/109), [PR 111](https://github.com/rqlite/rqlite/pull/111): Leader redirection
- [PR 104](https://github.com/rqlite/rqlite/pull/104): Handle the `-join` option sensibly when already member of cluster.

- [PR 96](https://github.com/rqlite/rqlite/pull/96): Add build time to status output.
- [PR 101](https://github.com/rqlite/rqlite/pull/101): Fix restore to in-memory databases.

- [PR 95](https://github.com/rqlite/rqlite/pull/95): Correctly set HTTP authentication.

- [PR 84](https://github.com/rqlite/rqlite/pull/84): Encrypted API (HTTPS) now supported.
- [PR 85](https://github.com/rqlite/rqlite/pull/85): BasicAuth support.
- [PR 85](https://github.com/rqlite/rqlite/pull/85): User-level permissions support.
- Print rqlited logo on start-up.
- End-to-end single-node and multi-node unit tests.