76b11a7247
previously the whirlpool step has been ignored when importing from a kbh database. on creation the whirlpoolstep would only be on a hardcoded 15 minute timer. I added the optional timer as argument to create_Whirlpool_Cooldown(). And made use of it for negative hops timer imported from KBH. For KBH databases this is valid because if the hops timer value is negative it can only be the whirlpool timer and the value is the time that is set for the brewing device for getting from boil to below 80°C. I did only test the data and not the functionality, but it sucessfully replaces the hardcoded "15" timer with the value from the first whirlpool hop addition while getting rid of the sign. |
||
---|---|---|
.devcontainer | ||
.github/workflows | ||
.vscode | ||
cbpi | ||
tests | ||
.dockerignore | ||
.gitignore | ||
cheat_sheet.txt | ||
chromium.desktop | ||
craftbeerpi.service | ||
craftbeerpi4boot | ||
Dockerfile | ||
LICENSE | ||
MANIFEST.in | ||
README.md | ||
release.py | ||
requirements.txt | ||
run.py | ||
sample.py | ||
setup.py | ||
testversion.py |
CraftBeerPi 4
CraftBeerPi 4 is an open source software solution to control the brewing and fermentation of beer 🍺.
📚 Documentation
Instructions on how to install CraftBeerPi and use its plugins is described in the documentation, that can be found here: gitbook.io.
Plugins
Plugins extend the base functionality of CraftBeerPi 4. You can find a list of available plugins here.
🧑🤝🧑 Contribute
You want to help develop CraftBeerPi4? To get you quickly stated, this repository comes with a preconfigured development environment. To be able to use this environment you need 2 things installed on your computer:
- docker
- visual studio code (vscode)
To start developing clone this repository, open the folder in vscode and use the development container feature. The command is called Reopen in container. Please note that this quick start setup does not work if you want to develop directly on a 32bit raspberry pi os because docker is only available for 64bit arm plattform. Please use the regular development setup for that.
For a more detailed description of a development setup without the development container feature see the documentation page: gitbook.io
Contributors
Thanks to all the people who have contributed