This is generally the best practice for production grade applications. For example, you might have loser permissions for a dev/qa environment but should have strict permissions for production. Similarly, you might have smaller instances for dev/qa to save cost and help performance tune but have larger instances for prod to account for higher traffic. Also, related to the first point, you can isolate each environments ENV/Settings/Runtime Variables per instance as per 12 factor applications. https://12factor.net/
Hope that helps, ~Blaine On Monday, May 7, 2018 at 9:28:28 AM UTC-5, Will H wrote: > > Hi all, > > Is it best practice to maintain different google cloud projects for each > environment (dev, qa, prod....) for all google cloud services. I.e. I mean > your dev project might have a google app, sql database, and compute > instance that mirror your prod (except of course for the feature you are > developing). Or do some people keep all their dbs, compute instance in one > project and only create separate projects for the dev, qa, prod version of > their google app engine? > > I hope that makes sense... > > Will > -- 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/c960175c-57ec-4d60-b870-bf28e4db235f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
