Re:A Developer's Worst Nightmare (The TinyGrab Story)
by rll on Sunday April 03, 2011 @11:29AM
(#2402926)
I must be missing something. How is it possible that they don't have umpteen copies of the sources checked out of whatever source control system they are using? Even if the central repository was destroyed, every developer should have a more or less recent version checked out somewhere.
[ Parent
| on HN ]
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by consultutah on Sunday April 03, 2011 @12:04PM
(#2403015)
We deploy from a special deployment repository. This has a bunch of advantages: 1) You can revert to a known state. 2) You can see if anything has changed on individual servers using svn stat. 3) You have a history of what has changed on production.
Any scm would work just fine.
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by zacharypinter on Sunday April 03, 2011 @11:51AM
(#2402986)
Looks like a PHP site. I'm guessing they weren't using version control and were instead just editing the files over FTP.
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by enko on Sunday April 03, 2011 @11:57AM
(#2402999)
If that turns out to be the case .. I wouldn't go so far as to say they deserved it, but my sympathy would definitely be pretty limited.
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by nwp on Sunday April 03, 2011 @12:16PM
(#2403047)
I agree. There is absolutely no excuse for not having some sort of source control and deployment system in place at an organization with a commercially deployed solution. Why would anyone regard such a system as optional? It is irresponsible.
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by Androsynth on Sunday April 03, 2011 @12:27PM
(#2403079)
so php == ignorance? are we really going to make that assumption? thats just foolish.
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by MichaelGG on Sunday April 03, 2011 @12:44PM
(#2403137)
No, but PHP easily allows a "edit source on server" as a deployment model.
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by random42 on Sunday April 03, 2011 @02:49PM
(#2403501)
Seriously, You dont even need a security attack for losing the changes with this model. A nice little "harddisk" failure would do the trick for you. :)
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by nupark2 on Sunday April 03, 2011 @12:52PM
(#2403156)
No, but given how often I've seen PHP developers do this, even at larger organizations, it's a plausible explanation.
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by zacharypinter on Sunday April 03, 2011 @12:41PM
(#2403129)
Not at all. Just trying to figure out how they might have a dev environment setup where there isn't a copy on local developer machines. Not all languages make that easy. PHP does.
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by Androsynth on Sunday April 03, 2011 @12:54PM
(#2403161)
ok, i get your point now.
They may have been using version control, but if they were checking out to a server and editing remotely, and that server happened to be the same server where the central repo was stored, it could explain how one attack would get it all.
Re:A Developer's Worst Nightmare (The TinyGrab Story)
by alinajaf on Sunday April 03, 2011 @04:37PM
(#2403869)
We're a PHP shop and we have version control. All but one of the companies I worked at used _some_ sort of version control, so it just doesn't make any sense that deploying an old release should be so tough.