Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Seperate environments, deploy from source control (Score 1) 66

Dev / Testing / Staging-Acceptance-PreProduction / Production

Each developer should get their own virtualhost on the dev server that can mimic production (apache virtualhosts if possible, or use vmware), that they can upload and self-test to. Use wildcard dns for hostnames like username.dev.company.com.

Depending on how many paralell things are tested, you might want more testing systems. Testing boxes should be mirrors of production software-wise (or at least as close as you feel comfortable).

Staging/Preproduction might be optional if you're a small shop or don't need acceptance testing - this should be a more stable place to do system tests outside of the possibly buggy testing environ. again, should mimic production, possibly closer.

production - obvious.

If you can do it, do deployments from SVN via labels or tags (not sure which it uses) like RELEASE_2006-12-27_NOTE (and something like RELEASE_LIVE which moves), so you can track revisions which are on production. Instead of copying code up, you use svn to sync code down, probably through some kickoff script. this occurs to each environment. Take everyone's access away from production, and probably staging - testing you might give select people access. Only the people in charge of the machines themselves, and whoever's in charge of releasing code should have access. Use automation with secure keys and stuff to do deployments.

automated tests happen in testing on a machine that can automatically sync itself to the latest checked in code.

Potentially, all of the above (cept for probably production) could easily be virtual machines.

Submission + - Origin of Quake3's Fast InvSqrt()

geo writes: "Beyond3D.com's Ryszard Sommefeldt dons his seersucker hunting jacket and meerschaum pipe to take on his secret identity as graphics code sleuth extraordinaire. In today's thrilling installment, the origins of one of the more famous snippets of graphics code in recent years is under the microscope — Quake3's Fast InvSqrt(), which has been known to cause strong geeks to go wobbly in the knees while contemplating its simple beauty and power. Enter the puzzle palace here."
Role Playing (Games)

Submission + - Gamers Rally to Save Online World

CleverNickName writes: "BBC says, "A collective of online gaming fans is making a bid to buy an online world and hand it over to the players.

The Free Ryzom Campaign is hoping to purchase the online fantasy game Ryzom from current owners Nevrax who will go into receivership in December."

The Free Ryzom guys are following in the footsteps of the people who bought Blender a few years ago. They have raised a significant amount of money — over 63,000 Euros as of this morning — toward their effort to purchase the game from Nevrax and make it free and open to all. Time is running out, though: on December 4, a judge and the liquidators will decide if the game can keep running or not. Depending on their decision, the Free Ryzom guys would then make their offer to buy the artwork, code, and game data. They think they could get it for as little as 10,000 Euros, but it's unlikely that their bid for the material will be unopposed, hence the need for a large war chest."

Slashdot Top Deals

Coding is easy; All you do is sit staring at a terminal until the drops of blood form on your forehead.