I must say that it is updated in a really strange way! BigWigs folder contains 39 (atm) versions of BW for example, many many updated mods are not yet reflected there....is it supposed to be so or new script is not running yet?
Agreed... I hope I didnt sound put off or annoyed. I do understand all the hard work, time and sweat you guys put into this. Working in an IT department myself, I totatly understand the lack of respect and understanding people have when there are technical issues.
I put everything up there on post-commit until we get moved to the new server, and get things set up in a pretty way.
When you're getting things set up in a "pretty" way, can I make on feature request? :)
It'd be really handy if the latest revision number can be put on the main page of the /files listing. Currently to parse the latest revision from /files, i need to hit the website once for each addon to get it's individual page. At least unless i'm missing some option/flag/parameter somewhere.
Anyway, if you can swing that, i'd be happy. But no worries either way.
I second have the latest zip in the /files dir, having to scrape each folder url looking for new files isn't very efficent :)
Well, I don't need the latest zip in the root of /files. Just an easy way to get the revision. I can manually form and hit the URL in a script, so thats not a big deal. :)
 Hmm, looks as though there's some amount of discrepancy between the revision number in latest.txt, and the latest zip available can be off. I imagine this is some kind of lag between the post-commit script updating latest.txt, and it actually checking out/zipping the addon. Can this be resolved? Maybe not update latest.txt until the zip has been put online?