Closed mudler closed 10 years ago
I think thats the deployer should be moved inside script/ and renamed too. I am going to create also an equivalent for mongodb and adjusting it doing it a bit more modular, in this way an installer could be easily developed
I placed there the delpoyer just to make tests on the schema but I agree with you. We must think about even on location of SQLite.db. Where should be placed? Is a good idea to ship a prepared db with the software or it's better an install script? Il 15/giu/2014 16:18 "mudler" notifications@github.com ha scritto:
I think thats the deployer should be moved inside script/ and renamed too. I am going to create also an equivalent for mongodb and adjusting it doing it a bit more modular, in this way an installer could be easily developed
— Reply to this email directly or view it on GitHub https://github.com/IntelliHome/Google-at-Home/issues/5#issuecomment-46116848 .
I think it's correct to place the db inside /var/lib/intellihome, like other linux sw do, i think that an example database it's necessary, like i have done for mongo (placed inside ex/ directory), but an installation/deployer script would be handy too, i'll prepare a pluggable draft for the scheme creation soon
the current database implementation require MongoDB and the IntelliHome::Parser::Mongo component to be set up on the master node to hold the plugins and voice triggers, this solution implemented is flexible but really resource-intensive, the goal is to make a SQLite backend (and thus the developing of IntelliHome::Parser::SQLite ) that will allow the installation of the master node also on low cost hardware ( like RaspberryPi ) with a proper test suite.