Don't use this in production - only for testing purposes

[djaiss]

If you read this, chances are that you are testing Chandler either locally or online.

Please keep in mind that we are in the development phase. Things are still unstable.

While we are not at the production level ready, we are continuously changing the database schema, as it's way easier to change the schema than to modify it once it's live.

For instance, in the next weeks, I'll completely refactor how we handle the concept of adresses. We could migrate the current structure but honestly it'll take much more time than rewriting it from scratch. The drawback: you'll need to flush your data in your DB for Chandler to work again.

[rubenv]

I'm guessing many of us are aching to start using this more intensively. Will you post a notice when it's safer to start testing it with more data (where we can sort of rely on it not to get lost)?

Stellar effort btw, thanks!

[djaiss]

I'm guessing many of us are aching to start using this more intensively. Will you post a notice when it's safer to start testing it with more data (where we can sort of rely on it not to get lost)?

Of course :-)

[jerodev]

I just started using Monica and wonder if I should use Chandler instead. Will there be a way to migrate from Monica to Chandler?

[djaiss]

I just started using Monica and wonder if I should use Chandler instead. Will there be a way to migrate from Monica to Chandler?

We want to provide one, but it'll take a lot of time, and Chandler will be made available before. So, use Chandler.

BUT we keep changing the data structure (take a look at the current pull requests). Don't use Chandler in production right now. We will release the stable, official v1 very very soon.