On Saturday, November 16, 2013 1:19:25 PM UTC-8, Lewis wrote: > > >> OK, web2py is back in business. At this point all of the problems are >> with one app that I copied from my web deployment (for some reason I lost >> the local version that synced properly with git when I transitioned from >> windows to mac). >> > > So, I just need to fix this one app and rebase to my git host. > > As noted earlier, it is always my fault (well, except maybe for the flawed > update in place feature). I just wish things didn't become my fault so > readily--as in, I wish there was much more of a deployment safety net. >
What version were you updating from? As of 2.6.1, there was a change in how you were supposed to deploy drivers and web2py.js, and the deployment button didn't have anything about that. I had some difficulty with the adminapp edit stuff, but that turned out to be mainly a browser cache issue. And subsequent to 2.6.1, the convention of versioning the static js files via a URL rewrite was turned on. Those who didn't try out 2.6.1 may have forgotten some of the notes about the deployment steps above. The one thing I can suggest for a deployment safety net is to have the update button give you a report of what drivers and static files (name, version, date?) that were present before and those that are present after. Somebody else have more ideas for what a deployment safety net might provide? /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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
