I'm with some problems here... I really hate .table files. That's my deploy routine:
1. download web2py from src 2. get my application from git and put inside web2py 3. remove some unused folders 4. backup my database 5. migrate my database structure *(that's the point!!)* 6. if ok, finished, else restore backup and last code 5 is my problem. I have a database structure and a lot of data but new code come with new table structure (that needs database migration). So I have some "fails": - If I maintain .table files into databases folder on localhost, than the hash is different from production hash (because connection is different). Solution: rename .table files for new db._uri_hash (It's not so beautiful) - If I set migrate=False I need to do migrations setting sql into my mysql database (not good and I'm doing by now). - If I not mantain .table files I need fake_migrate from previews deploy and than migrate. Looks good but need a lot of extra work and I don't know if it work. What's the best way? Are there new suggestions? -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
