foesi / bierwo Goto Github PK

Some kegs are only for fermentation.
Brews are first stored in this special kind of kegs.
They are especially accessible from the brew view.
They are not shown in the keg list when filled.

Maybe it is possible to return a content type so android or ios can automatically open the barcode scanner app.

When emptying a keg, the date will be noted.
So we see how long the content of a keg survives.

there should be some default locations and only if a new location should be used the location should be inserted automatically.

access with form.errors

Currently, QR codes are generated on keg generation or if the action is invoked in the keg view.
On every deployment of the application, all old QR Codes are deleted.
Maybe it does not make any sense to include the QR Codes in the web interface, but generate them dynamically on request or only when generating print templates (see #3)

An amount of bottles can be connected to a brew and a new qr code for the brew or the bottles belonging to a brew can be generated.
When removing, drinking or giving bottles aways from the storage, the QR Code can be scanned and the amount of bottles can be subtracted from the initial amount.

Add possibility for a (client-side) sorting of table contents.

If Kegs are no longer used, there should be the possibility to deprecate old kegs.

In the detail views for brews or kegs there should be a Home button for the respective keg or brew list.

Make it possible to correct or add information.

For easily printing the qrcodes for the kegs, there should be a printer template.
This template should include at least the qr code of the keg for showing the show_keg.html view and the kegs name for easily identifying the corresponding keg.

Next to the qr code for showing the kegs, there could be other qr codes for easily accessing a keg specific action.
Those actions can be:

• showing the keg view (show_keg.html)
• filling the keg
• emptying the keg
• adding a new comment or location

Add the possibility for adding comments to kegs.
This includes the location of the keg.
So when changing the location of a keg, a new comment with a new location has to be created.
The default location on adding a new comment should be the last known location.
The comments should be sorted from newest to oldest in the show_keg.html view.