Thanks for the clarification. It makes sense to to use the same behaviour as a w2p file deploy, though it would be good if it said so somewhere, and also that this should only be used for first time deployments, accidentally point this to an app that already exists and you risk serious migration headaches!!
On Friday, January 27, 2017 at 5:55:04 PM UTC, Leonel Câmara wrote: > > > I nerve-wrackingly went to submit the form, but it failed saying the > username already exists - does this mean it even tries to register me? > > Yes it does register you for a free pythonanywhere account if you are not > registered. This is meant to be a very easy way of getting your project > online. > > > And what if the app does already exists? Will it make sure not to > overwrite the tables and sessions directories and so on? > > It does basically the same thing that happens when you deploy using a .w2p > file. Yes it will overwrite by default and I have not made the option not > to overwrite yet. > > For now the databases folder goes too so the tables are overwritten too. > The excluded folders are "cache", "sessions" and "errors". > > Note that this is exactly the same behavior you get when you create a w2p > file of your application in admin and then install the application in > pythonanywhere using the admin of a previously installed web2py. > > -- 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.
