Fork Your Application's Data (Not Just Your Code)

Re:Fork Your Application's Data (Not Just Your Code) by thibaut_barrere on Thursday November 08, 2012 @05:03PM (#4760126)

It's fairly common and works pretty well if you have a good test coverage and monitoring in place.

GitHub is a documented example (and I happen to deploy branches daily too :-):

https://github.com/blog/1241-deploying-at-github

[ Parent | on HN ]

Re:Fork Your Application's Data (Not Just Your Code) by amatix on Thursday November 08, 2012 @05:35PM (#4760270)

I've read several times about github's use of branches in deployment/production. How are DB schema/data migrations handled (and kept safe/sane)? Presumably hubot and friends prevent Bad Things from happening by deploying a branch that doesn't match the current DB state?

[ Parent | on HN ]

Re:Fork Your Application's Data (Not Just Your Code) by wahnfrieden on Thursday November 08, 2012 @09:19PM (#4760932)

I didn't say one way is strictly better. There are tradeoffs to consider and that's all that really matters. I'm not sure it occurred to the OP that there are benefits to forgoing remote branches, so I mentioned it.

[ Parent | on HN ]

Re:Fork Your Application's Data (Not Just Your Code) by thibaut_barrere on Friday November 09, 2012 @03:17AM (#4761880)

My bad, I read "Consider not doing that." as a more strict recommendation!

[ Parent | on HN ]

Re:Fork Your Application's Data (Not Just Your Code) by wahnfrieden on Friday November 09, 2012 @05:16PM (#4764972)

Sorry, I was too blunt :)

[ Parent | on HN ]