That directory structure changes about as often as there are new official releases, as you can tell by all of the orphan build directories. Linking straight into the repository won't let me pick up new vehicles, and will break when vehicles go from "experimental" to "production" status. The release notes aren't in the repository (AFAIK), so I have to enter those links manually as well. Given that I have to manually update the page, I figure it's more reliable to ferret out the right versions for each vehicle and copy them to my site. This way, my page keeps working even if the repository changes, which means less work maintaining the page between releases (which is currently zero effort). Anyone who's really into getting the latest builds can just grab the files from the repository. My page is to support those who don't care enough to climb that learning curve. Tom on 1/14/13 1:23 PM, Michael Balzer wrote:
Thanks, Tom!
Hm... to optimize the rollout, have you tried to link directly to the repository files?
The links in vehicle/firmware don't work, but using the github file browser I can get for example...
https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/master/vehicle/... MS.X/dist/V2_Experimental/production/OVMS.X.production.hex
I'm new to github, but that URL scheme looks like being designed as a permanent link.
Regards, Michael
Am 14.01.2013 21:13, schrieb Tom Saxton:
The firmware update guide page now has version 2.2.2 builds up.
http://www.idleloop.com/tesla/ovms/
Tom
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev