Best practice for production and test environments in Google App Engin -

Best practice for production and test environments in Google App Engin -

what best practices production , test (staging) environments in google app engine? thought setup separate projects?

we utilize google cloud storage , cloud sql. i'd prevent accidents mistakenly working in production when intend work in test.

we'll storing lot of stuff in gcs. understanding gcs environments separate between projects. can desirable us. but, if want re-create product test, possible duplicate gcs 1 app another?

looking forwards hearing how others this.

i can see 2 ways this, depending on needs:

1) using versions on app, different instance in cloud sql , different bucket name gcs can utilize same project. have super careful setting target each of calls go , re-direct them when goes live.

2) using separate project safer alternative either way need utilize unique bucket name. bucket names must unique across gcs instances.

its quite easy re-create 1 bucket 1 time permissions setup. using gsutil can re-create bucket bucket.

google-app-engine