On Saturday, August 30, 2014 9:15:37 PM UTC-7, Diogo Munaro wrote: > > Hey guys, I was thinking about web2py migrates and how control database > version. > > I did a workflow that take care of database version control and it's > extensible for a lot of version controls (like git or mercurial, but by now > only git) and databases (by now only mysql and postgres, but extensible > too). > > Looks interesting. I haven't worried too much about migrations yet because I dont' have a "real production" environment, but it certainly looks like it will be worth studying the flow chart, so I printed it out.
I'm a Mercurial type myself, but I don't know how much testing I can help with. If I can, though, I will. (I'm also a sqlite type, though I've used Postgres in class.) > This workflow could be useful with Continuous Integration environment. > > It's open for all kind of usage and is here for more information: > https://github.com/dmvieira/web2py-migrate > > I'll love collaboration and feedback ;) > > Regards > Thanks! /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
