CocktailPi VS CocktailBerry

Background - I'm trying to do this project: https://github.com/alex9849/pi-cocktail-maker. I can't tell how exactly the components are connected to each other on the circuit board. It doesn't make sense to me that the blue wires would be so far away from the other components unless the circuit board is the type where all components on a row are connected by a copper strip. I already started soldering everything together on the type of board where the holes are not connected. Any advice is appreciated!

Do you mean the hardware? I added a what-to-buy list on the github page: https://github.com/alex9849/pi-cocktail-maker For the software that's self programmed. I used VueJS, Spring Boot and the pi4j library for that.

So this is my cocktailmaker project. I've only shown the cocktail miking feature since I wanted to keep the video short. But you can check out the github page: https://github.com/alex9849/pi-cocktail-maker Theses also a little explanation how this project could be recreated. I've also set up a demo site if you want to check out the webinterface by yourself: https://cocktailmaker-demo.liggesmeyer.net/ User: admin password: 123456

Hey there, creator of CocktailBerry, which heavily utilizes PyQt. For me, the footprint/memory usage is a thing, because running on microcomputers (RPi, often only 1 GB Ram) and a Desktop variant of the OS won’t have that many resources for other things. If you want to run one or more docker containers in the background, while also ensuring a seamless operation of your app, this is even more important. Running Chrome in a Kiosk mode works but takes way more spin-up time and response time. For regular desktop projects, I would probably use some web-based framework and maybe bundle it with electron in the end, since memory usage is not so important and, let's be honest, you have much more options and individualization. But developing Qt (especially with the PyQt port) is not slow either. And having a model, view, and controller monolith can benefit or speed up development if you want to also interact with physical components on the pi and have feedback/data streams compared to the frontend/backend + REST approach. I have to admit that styling is quite a pain compared to modern web CSS. PyQt offers QSS, which is some sort of pseudo-CSS, but like from the 90s. So many modern features are lacking. But using some SASS adoption for QSS can even enable you common templates and translate them into different styles, for example. Sometimes, you just need some workaround for options, which would be one line in today’s CSS. And in the end, even if the documentation is not that good like other projects, it’s not horrible either. There are a lot of openly accessible tutorials for beginners, as well as the qt designer/creator for a more visual “drag and drop” creation approach of the application, which may be a plus for some users.

If you want to have some insights, it’s also Open source: https://github.com/AndreWohnsland/Cocktailmaker_AW

Awesome build. I like the approach you took! I can tell out of experience getting suitable pumps can be one of the most challenging parts… I’ve also build a Cocktail machine with a touch display, here is the code and some impressions, if someone is interested: https://github.com/AndreWohnsland/Cocktailmaker_AW