ensure that .centinel directory is created on startup for server

[ben-jones]

If the .centinel directory does not exist for the server, it gives very obtuse messages like "sqlalchemy.exc.OperationalError: (OperationalError) unable to open database file None None". The config file should create the directory if it doesn't exist

[gsathya]

I think this should go in the https://github.com/iclab/centinel-server repo not here?

[ben-jones]

@gsathya, I wanted to centralize all of our issues here in iclab/centinel, but I could be convinced of a need to have separate issue trackers.

[gsathya]

@gsathya, I wanted to centralize all of our issues here in iclab/centinel, but I could be convinced of a need to have separate issue trackers.

But it doesn't make sense to have these here? since the code lives in another repo?

[ben-jones]

@gsathya, yes, but this is the same project. We will duplicate issues rather than having a server and a client piece together as one issue.

[gsathya]

Na, GitHub makes it super easy to reference issues so you don't have to worry about anything like that.

Imagine a potential contributor who knows flask but nothing about centinel and finds the centinel-server repo. Now they're trying to find a issue to hack on but don't realise that all issues are in iclab/centinel. We've now lost a valuable contributor!

[ben-jones]

@gsathya, is there an easy way to reference issues between repos? If so, then I say we go with separate issue trackers

[gsathya]

@gsathya, is there an easy way to reference issues between repos?

See #33 (comment)

[gsathya]

(If you meant reference with respect to milestones then no)

[ben-jones]

@gsatha, I'm closing this issue and will recreate it on the server

[gsathya]

@gsatha, I'm closing this issue and will recreate it on the server

Thanks! 👍