codemonger.org -- Server back up!

[daniel.santos]

codemonger.org is down again.   I have a call into tech support and hope to get it back up asap.

[daniel.santos]

There appears to be a hardware problem on the server.  I can't tell if it's the power supply or the motherboard but I'm going in tomorrow to troubleshoot and work on it.  I don't have a motherboard to replace it with right now, so if it's not the power supply, I'm probably going to stick in a cheap computer temporarily until I can get a new mobo (which will have to be next month as $ is limited).  If anybody has an AM2 compatible motherboard with SATA they wish to donate, please let me know.

Daniel

[daniel.santos]

I got the server fixed and I'll be re-installing it tomorrow.  I'll post a new thread when it's back up.  This has given me a bit of pause, and though I like being able to have full control over the repository, maybe it would be a good idea to at least mirror it on sourceforge.  I've been reading up on how you do the dump.  What is your opinion hailstone?  It would be nice if there was a way to cluster two svn instances, but I don't know much about how that would work (if it's possible).

[daniel.santos]

w00t! I got codemonger.org back up!  It's running from my home right now, so it wont be as fast but tomorrow I'll be taking it back in to my hosting provider where it's usually co-located.  Only the main web site and subversion repository is up, I have the bug database down while it's here (due to IP-address issues).  If you have problems, you may have an old DNS entry cached.  The current address is 70.242.117.69, although this will be reverted some time tomorrow (and the server will be down for another hour or so as well).  Thanks everybody for your patience.

[hailstone]

It's good you have it working again. It seems just as fast if not faster than before (unless it's already there  ???).

I think it is good to have sourceforge mirror the GAE files but to make it easier I think techs and tilesets should move to its own project dir since they don't change much between the versions. This will save about 200MB per branch/tag leaving about 60MB. Maybe tags should only be stored on codemonger (~260MB * 12+ = large)? Are we going to use the trunk?

I haven't done mirrors with SVN but I found out v1.4 comes with svnsync and sourceforge uses v1.5. You'll need admin access if you want to start messing around with the sourceforge repositories.

http://blog.codefront.net/2007/03/29/setting-up-svnsync-ed-mirrored-svn-repositories-on-ubuntu-part-1-of-2/
http://wordaligned.org/articles/how-to-mirror-a-subversion-repository
http://svn.collab.net/repos/svn/trunk/notes/svnsync.txt
http://apps.sourceforge.net/trac/sourceforge/wiki/Using%20rsync%20for%20backups

[daniel.santos]

Nope, I haven't moved it yet, so that'd odd.

I like the idea of moving techs and tilesets into their own project strictly for the sake of componentizing them, since you can really plug in any tileset and techtree that you want.  However, there is no additional storage requirements on the server because subversion is very smart about that type of thing.  When you create a new tag or branch, subversion only stores the information about each file and revision of that file, it never actually copies anything.  In fact, the entire subversion repository on codemonger (including the FPM tree) only takes 101 MiB of disk space and contains all of the revision history for over a year.

So I'm using v1.5.5 on the server (I just upgraded from 1.5.4 yesterday).  I like the idea of doing the svnsync thing, perhaps we'll continue to do our check-ins into codemonger and keep the sourceforge repository in sync?  I'll have to read your links to figure that out, thanks!

EDIT: hmm, it would seem it might make more sense to do it the other way around?  I'm not sure now

[hailstone]

When you create a new tag or branch, subversion only stores the information about each file and revision of that file, it never actually copies anything.

That makes sense.

I think have sourceforge repository as main then use rsync to make backup on codemonger. This way we can use the pre-setup commit hooks and statistics features of sourceforge. Probably easier user management too.