Got a BOL for another 800ish pounds of coffee. This one won't need any product development work because it's a shipment from coffee under forward contract (forward contracts with a delivery spread are a common tool to ensure availability of a specific coffee, spread the cost over time, and not need as much on site storage) and I've already gotten some of it. I still have the same amount on contract to ship later in the year.
@jamey Agreed.
@jamey Yes, that would be nice to have, but at the same time I'm so glad to be off servers like that. FTP updates run a lot slower and it's easy to end up with things being temporarily broken for people visiting mid-update, especially on larger updates or naive update strategies.
@jamey My preferred setup for something like this is to just have git running on the deployment server and use a hook there to deploy updates on commit to a specified branch. Then deployment just looks like git push origin master. Not quite push button, but pretty close.
This is a case where the download link is really handy. Lots of instructors don't know how to download from legacy tube and terrible Internet connectivity is pretty common at instruction venues so if people are using my stuff like that I'd really prefer them to be able to fetch that in advance rather than break the class flow with technical difficulties.
Author of Typica software for coffee roasters.