Page 1 of 1
HomeBrew Software
Posted: Tuesday Apr 26, 2005 5:50 pm
by Robjess
Can anyone recommend some software to help me keep track of my brews??
What do other people use - note book? excel? Memory?
Posted: Tuesday Apr 26, 2005 5:59 pm
by pelican
i use a note pad with all the details and a batch number, i then wright this number on all the caps on bottles with a marker pen
Posted: Tuesday Apr 26, 2005 6:10 pm
by Evo
There's a long post about this topic from before. Have a look through.
Posted: Wednesday Apr 27, 2005 11:14 am
by anti-fsck
Aah, the beer log.
Consists of a dedicated, headless PIII 650MHz IBM Netfinity 1000 running Debian woody, hosting a SQL/Apache-driven PHP Nuke website[1].
Some may say it's overkill, but meh, I get by.
[1] The more technically au fait home brewer may note with some alarm that PHP Nuke is little more than a script kiddie's root shell masquarading as a news blog front-end, but so far, so good.
Posted: Wednesday Apr 27, 2005 2:52 pm
by General
Similar to Anti-FSCK I use a dedicated laptop.
P1 32Mb ram 750mb hard disk, running windows 98, and has a modified Cascade Breweries brewcard that I downloaded and altered to my own specs, good for working out alcohol, I altered it to correct for hydrometer reading/temperature.
I'm buying a handheld shortly and will migrate the spreadsheet to that for more convenience.
Posted: Thursday May 05, 2005 12:08 pm
by Oliver
I use a notebook (paper, not computer).
On the front it says:
Name: Oliver
Subject: Beer
Here's the thread about brewing software:
http://www.homebrewandbeer.com/forum/vi ... .php?t=580
Cheers,
Oliver
Posted: Saturday Jun 25, 2005 9:53 pm
by anti-fsck
anti-fsck wrote:Aah, the beer log.
Consists of a dedicated, headless PIII 650MHz IBM Netfinity 1000 running Debian woody, hosting a SQL/Apache-driven PHP Nuke website[1].
Some may say it's overkill, but meh, I get by.
AAAAAAAAARGH.
Then there are days like today when the usually flawless software upgrade bjork bjork bjorks.
My record of home brews simply reads:
"There seems to be a problem with the MySQL server, sorry for the inconvenience. We should be back shortly."
Dammit. It won't be shortly.