I cancelled my Amazon account, and don't currently plan to have a new one soon. I have access to more hardware, though, and plan to make more resources available for MG soon. This will include a continuous integration system (Jenkins), which Softcoder already setup these days (currently reachable at ci.megaglest.org - but it will become unavailable for some days shortly). The CI will be able to trigger and evaluate both local and remote builds of MegaGlest. It would be great if we could link your server to it (once it's ready for this), so that we would both have Windows builds produced on the fly (more or less) triggered by SVN commits, but also be able to evaluate the build process (and possibly do some automated quality testing, too) centrally.
About the hostname, I'll be happy to set one, but I'm unsure about the name. Taking into account that we may also have Linux (and possibly, in a distant future, OS X builds), I guess it makes more sense to have a nightly.megaglest.org website pointing to the download locations of both Linux and Windows builds. Which could, for example, take the form of w32.nightly.megaglest.org (pointing to your server). Do you think that's a good naming scheme and general approach?