v0.03 -- maint release

Showing 1-3 of 3 messages
v0.03 -- maint release wes 9/27/12 5:52 AM
as promised:

http://code.google.com/p/collective-intelligence-framework/downloads/detail?name=cif-v0.03.tar.gz

please note, you must install the CPAN module: Try::Tiny first via:

$ sudo perl -MCPAN -e 'install Try::Tiny'

which is reflected in the ServerInstall_v0 doc too.

i also added a:

$ make purgedb

which will allow you to purge your database and start over again if your database gets out of whack. it will leave your apikeys in-tact:

https://github.com/collectiveintel/cif-v0/blob/master/schemas/pg_purge.sql

just need to make sure you comment out and kill your crons before running the script.
--
Wes
wesyoung.me

Re: [ci-framework] v0.03 -- maint release Dave Dittrich 9/27/12 9:02 PM
On Thu, Sep 27, 2012 at 5:52 AM, Wes Young <w...@barely3am.com> wrote:

> i also added a:
>
> $ make purgedb
>
> which will allow you to purge your database and start over again if your database gets out of whack. it will leave your apikeys in-tact:

Any updates on when a database porting tool will be available?  I am
using CIF in a production system and am trying hard to avoid whacking
the database or starting over. I still haven't tackled porting the
data from an earlier CIF instantiation and am occassionally querying
both the current and old databases in sequence when need be. Having
the ability to export/import/upgrade the database contents would yield
you many beers! :)

--
Dave Dittrich
dave.d...@gmail.com
Re: [ci-framework] v0.03 -- maint release wes 10/2/12 12:01 PM

On 2012-09-28, at 12:02 AM, Dave Dittrich wrote:

> Any updates on when a database porting tool will be available?  I am
> using CIF in a production system and am trying hard to avoid whacking
> the database or starting over. I still haven't tackled porting the
> data from an earlier CIF instantiation and am occassionally querying
> both the current and old databases in sequence when need be. Having
> the ability to export/import/upgrade the database contents would yield
> you many beers! :)

no updates yet, although RC1 is due out any day now (we're doing some of the last load testing, doc testing as we speak).

past that i have some more API work to doc/finish and then it's on to the data tool stuff.

so, i'm about a month or so behind where i'd like to be (had to do a re-write of v1 due to some underlying flaws with my orig logic), i'd put this at another month or two (fall travel pushes us back a few weeks) maybe?

agreed. database is a pain to get rid of, we're reaching:

/dev/mapper/XXX-archive
                      197G  128G   60G  69% /mnt/archive
/dev/mapper/XXX-index
                      197G  169G   25G  88% /mnt/index


on our prod instance, which is coming up on it's year anniversary in Dec. where we'll have to do some deciding too.

in the short run, there'll be a conversion tool, in the long run i've got some things on my list around "aggregation and partition management" that i just haven't had a chance to do yet that'll fold nicely into the long-term data-management strategy.

stay tuned,
--
Wes
wesyoung.me