Hello, I in the process of writing Disaster Recovery Plan/Package... I was seeking what would be a good poor man's way to make sure to keep iterative development history and working framework and app package.
I was realizing that I did a poor job at keeping track of application dependencies and in the first place which web2py version the app may requires as web2py has evolve overtime some features are not present in previous version... I can thought of keeping a file detailing the applicaiton dependency versionned beside the reste of the app in a format that allow deployment routine to exploit this file to make sure deployment is realize with proper web2py and dependencies... I already had such a kind of deployment routine with fabric, but nothing is write down other then specify to deploy function where to take framework and app version for the deployment... Having a file prescribing the requirement that the deploy function should enforce appears to me a good tradeoff between my actual situation and something a bit overkill for now like Anisible et al. I also thought about using a git repot to attach ready to deploy package and use this repository as kind of deployment server, so app and framework at least are attached together, I just have to point over the rigth/last git tag my deployment fabric function... But how are you doing it ? Thanks Richard -- 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.
