I updated my repo with Vagrant and bash scripts to install Cassandra 2.0.3
https://github.com/stealthly/scala-cassandra/
0) git clone https://github.com/stealthly/scala-cassandra
1) cd scala-cassandra
2) vagrant up
Cassandra will be running in the virtual machine on 172.16.7.2 and is
accessible f
I think i will invest the time launching cassandra in a forked forground
process, maybe building the yaml dynamically.
On Friday, December 27, 2013, Nate McCall wrote:
> I've also moved on to container-based (using Vagrant+docker) setup for
doing automated integration stuff. This is more difficul
I've also moved on to container-based (using Vagrant+docker) setup for
doing automated integration stuff. This is more difficult to configure for
build systems like Jenkins, but it can be done and once completed the
benefits are substantial - as Joe notes, the most immediate is the removal
of varia
I have been using vagrant (e.g. https://github.com/stealthly/scala-cassandra/ )
which is 100% reproducible across devs and test systems (prod in some cases).
Also have a Docker setup too
https://github.com/pegasussolutions/docker-cassandra . I have been doing this
more and more with clients t
Hi Ed,
my opinion on unit testing with C* is: Use the real database, not any
embedded crap :-)
All you need are fast truncates, by which I mean:
JVM_OPTS="$JVM_OPTS -Dcassandra.unsafesystem=true"
and
auto_snapshot: false
This setup works really nice for me (C* 1.1 and 1.2, have not tested 2.0
ye
