BRBU Builds a bar bot

[FlyingMongoose]

Recipe database select based upon available ingredients.

So a relational databse.

[KarthXLR]

I think we've found our prototype

[HeK]

I think we've found our prototype

I think we can do better than a 404 page.

[FlyingMongoose]

[quote author=Karth link=topic=7513.msg285899#msg285899 date=1438910178]
I think we've found our prototype

I think we can do better than a 404 page.
[/quote]

I don't know... you may be asking a bit much here...

[at0m]

[quote author=HeK link=topic=7513.msg285893#msg285893 date=1438896396]
Recipe database select based upon available ingredients.

So a relational databse.
[/quote]I really don't think it's going to need a SQL server. I don't think there is going to be enough data to make that worthwhile.

Sent from my Nexus 5 using Tapatalk

[FlyingMongoose]

So what? Keyvalue style flat file or something like nosql ultimately I'd like to not hard code the recipes

Sent from my Nexus 7 using Tapatalk

[Greatbacon]

[quote author=FlyingMongoose link=topic=7513.msg285895#msg285895 date=1438898842]
[quote author=HeK link=topic=7513.msg285893#msg285893 date=1438896396]
Recipe database select based upon available ingredients.

So a relational databse.
[/quote]I really don't think it's going to need a SQL server. I don't think there is going to be enough data to make that worthwhile.

Sent from my Nexus 5 using Tapatalk


[/quote]It's not like it's particularly hard or resource intensive to stand-up a sql server, and it gives us room to expand feature sets down the road.

edit: I personally wouldn't mind taking the chance to play around with MongoDB, but I know that also falls under the same criticism.

[FlyingMongoose]

[quote author=atm0m link=topic=7513.msg285903#msg285903 date=1438955282]
[quote author=FlyingMongoose link=topic=7513.msg285895#msg285895 date=1438898842]
[quote author=HeK link=topic=7513.msg285893#msg285893 date=1438896396]
Recipe database select based upon available ingredients.

So a relational databse.
[/quote]I really don't think it's going to need a SQL server. I don't think there is going to be enough data to make that worthwhile.

Sent from my Nexus 5 using Tapatalk


[/quote]It's not like it's particularly hard or resource intensive to stand-up a sql server, and it gives us room to expand feature sets down the road.

edit: I personally wouldn't mind taking the chance to play around with MongoDB, but I know that also falls under the same criticism.
[/quote]
Mayhaps this become a marketable product. Wouldn't it be cool to have a WiFi enabled device that connected to a database that can be updated by outside sources? Charge a fee for premium services and provide a display that shows what each reservoir should have to mix which drink.

But that's getting way ahead of ourselves. Honestly on a 16 or 32gb SD card on a pi running python and mysql for local stuff it will work perfectly fine and plenty fast on a pi 2.

Sent from my SCH-I545 using Tapatalk

[StolenToast]

[quote author=Greatbacon link=topic=7513.msg285906#msg285906 date=1438969123]
[quote author=atm0m link=topic=7513.msg285903#msg285903 date=1438955282]
[quote author=FlyingMongoose link=topic=7513.msg285895#msg285895 date=1438898842]
[quote author=HeK link=topic=7513.msg285893#msg285893 date=1438896396]
Recipe database select based upon available ingredients.

So a relational databse.
[/quote]I really don't think it's going to need a SQL server. I don't think there is going to be enough data to make that worthwhile.

Sent from my Nexus 5 using Tapatalk


[/quote]It's not like it's particularly hard or resource intensive to stand-up a sql server, and it gives us room to expand feature sets down the road.

edit: I personally wouldn't mind taking the chance to play around with MongoDB, but I know that also falls under the same criticism.
[/quote]
Mayhaps this become a marketable product. Wouldn't it be cool to have a WiFi enabled device that connected to a database that can be updated by outside  sources? Charge a fee for premium services and provide a display that shows what each reservoir should have to mix which drink.

But that's getting way ahead of ourselves. Honestly on a 16 or 32gb SD card on a pi running python and mysql for local stuff it will work perfectly fine and plenty fast on a pi 2.

Sent from my SCH-I545 using Tapatalk
[/quote]

We might want a better dev board that can support all the pumps it would need.

[FlyingMongoose]

[quote author=FlyingMongoose link=topic=7513.msg285907#msg285907 date=1438969518]
[quote author=Greatbacon link=topic=7513.msg285906#msg285906 date=1438969123]
[quote author=atm0m link=topic=7513.msg285903#msg285903 date=1438955282]
[quote author=FlyingMongoose link=topic=7513.msg285895#msg285895 date=1438898842]
[quote author=HeK link=topic=7513.msg285893#msg285893 date=1438896396]
Recipe database select based upon available ingredients.

So a relational databse.
[/quote]I really don't think it's going to need a SQL server. I don't think there is going to be enough data to make that worthwhile.

Sent from my Nexus 5 using Tapatalk


[/quote]It's not like it's particularly hard or resource intensive to stand-up a sql server, and it gives us room to expand feature sets down the road.

edit: I personally wouldn't mind taking the chance to play around with MongoDB, but I know that also falls under the same criticism.
[/quote]
Mayhaps this become a marketable product. Wouldn't it be cool to have a WiFi enabled device that connected to a database that can be updated by outside  sources? Charge a fee for premium services and provide a display that shows what each reservoir should have to mix which drink.

But that's getting way ahead of ourselves. Honestly on a 16 or 32gb SD card on a pi running python and mysql for local stuff it will work perfectly fine and plenty fast on a pi 2.

Sent from my SCH-I545 using Tapatalk
[/quote]

We might want a better dev board that can support all the pumps it would need.
[/quote]

There's plenty of i/o on a Pi, plus room for expansion, lastly, HeK has a fuckton of them... unless he bought those boxes of them for work.

Ultimately though there are plenty of i/o board options too.

[Greatbacon]

[quote author=FlyingMongoose link=topic=7513.msg285907#msg285907 date=1438969518]
[quote author=Greatbacon link=topic=7513.msg285906#msg285906 date=1438969123]
[quote author=atm0m link=topic=7513.msg285903#msg285903 date=1438955282]
[quote author=FlyingMongoose link=topic=7513.msg285895#msg285895 date=1438898842]
[quote author=HeK link=topic=7513.msg285893#msg285893 date=1438896396]
Recipe database select based upon available ingredients.

So a relational databse.
[/quote]I really don't think it's going to need a SQL server. I don't think there is going to be enough data to make that worthwhile.

Sent from my Nexus 5 using Tapatalk


[/quote]It's not like it's particularly hard or resource intensive to stand-up a sql server, and it gives us room to expand feature sets down the road.

edit: I personally wouldn't mind taking the chance to play around with MongoDB, but I know that also falls under the same criticism.
[/quote]
Mayhaps this become a marketable product. Wouldn't it be cool to have a WiFi enabled device that connected to a database that can be updated by outside  sources? Charge a fee for premium services and provide a display that shows what each reservoir should have to mix which drink.

But that's getting way ahead of ourselves. Honestly on a 16 or 32gb SD card on a pi running python and mysql for local stuff it will work perfectly fine and plenty fast on a pi 2.

Sent from my SCH-I545 using Tapatalk
[/quote]

We might want a better dev board that can support all the pumps it would need.
[/quote]

If it gets to the point where we feel like we need more pumps, we can start talking about switching out boards.  But considering we don't even have one pump hooked up, we might be getting ahead of ourselves.

[kaese]