No description
Find a file
Ben Johnson b06ecf3320 Update import path
This commit updates the import path from:

```
pilosa/*
```

to:

```
github.com/umbel/pilosa/*
```

This follows standard Go convention and makes the project "go gettable".

The README was also updated to reflect the changes.
2015-08-05 22:50:38 -06:00
commands/pilosa Update import path 2015-08-05 22:50:38 -06:00
config Update import path 2015-08-05 22:50:38 -06:00
core Update import path 2015-08-05 22:50:38 -06:00
cruncher Update import path 2015-08-05 22:50:38 -06:00
db Update import path 2015-08-05 22:50:38 -06:00
dispatch Update import path 2015-08-05 22:50:38 -06:00
executor Update import path 2015-08-05 22:50:38 -06:00
hold Update import path 2015-08-05 22:50:38 -06:00
index Update import path 2015-08-05 22:50:38 -06:00
interfaces Update import path 2015-08-05 22:50:38 -06:00
query Update import path 2015-08-05 22:50:38 -06:00
transport Update import path 2015-08-05 22:50:38 -06:00
util Update import path 2015-08-05 22:50:38 -06:00
.gitignore Update import path 2015-08-05 22:50:38 -06:00
default.yaml added default config file 2015-08-03 11:52:53 -05:00
deps.json Update import path 2015-08-05 22:50:38 -06:00
README.md Update import path 2015-08-05 22:50:38 -06:00

pilosa

Pilosa is a bitmap index database.

Getting Started

To download the source, run go get:

$ go get github.com/umbel/pilosa

You can update the dependencies to specific versions using depman:

$ go get github.com/vube/depman

And then run depman from the project directory:

$ cd $GOPATH/src/github.com/umbel/pilosa
$ depman

Now you can install the pilosa binary:

$ go install github.com/umbel/pilosa/...

Pilosa requires that etcd is running locally for coordinating the cluster:

# In another terminal window
$ etcd

Now run pilosa with the default configuration:

PILOSA_CONFIG=default.yaml pilosa

This setup assumes that cassandra and etcd are running locally and that cassandra keyspace pilosa has been setup as describe in the file index/storage_cass.go.

If you don't want backend storage you can comment out storage_backend in the yaml file and it will just operate out of memory.