3. In addition when one has a bug and the site does not deploy properly being without the intermediate stage makes debugging more difficult.
Nigel On Wednesday, 21 December 2016 20:36:57 UTC, Joshua Smith wrote: > > Having used both, the GUI is much better in two cases: > > 1. When you have a lot of projects, it’s nice to have the GUI to just > click and update, vs having to root around finding the right script to run. > > 2. I could train a non-programmer to push an update to a web app using the > GUI. Not so using the command line. > > Also, the whole setup for the command line is really focused on the idea > that you’ll have only one project, which is pretty silly. So you end up > having to write simple scripts as wrappers around the command line stuff, > just to pass project names. > > And one other issue with the command line that was really just a violation > of the principle of least surprise: deploying should NOT route all traffic > to the version you just pushed. That’s insane. Whoever thought that was a > good default clearly has no experience developing real applications. Not a > big deal to work around because I have to write the aforementioned wrapper > scripts anyway, but… seriously? > > -Joshua > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/de0b2b9e-c591-4949-a2eb-96488c2c414c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
