Thanks for the reply. It's really not obvious to me with the current docs how to do this but I'll dig more into it. I don't want to actually take ownership of the domain under an account until I understand how it works since we need this to be the 'official' domain account.
If I understood correctly I can have an account [email protected] own the domain, then have a [email protected] own some apps, and have a [email protected] own some other apps, and somehow both of these can use example.com as their domain? Thanks, Dre On Jul 30, 12:49 am, "l.denardo" <[email protected]> wrote: > The account used for domain management has nothing to do with the ones > used for deploying. > > You can have a team working on dev.appspot.com, mapped to your dev > subdomain, another one completely different working to production, > e.g. on prod.appspot.com mapped to your production subdomain, and let > your company domain administrator (who does not have to be in neither > of the two teams) map your cname records. > > Differently stated, use one account for DNS management, and only for > that, and let the two teams work on completely separate apps on > appspot. > > Regards > Lorenzo > > On Jul 30, 2:21 am, Dre <[email protected]> wrote: > > > Yes, this would work for deployment in a small group, but this doesn't > > work so well for Enterprise deployments where multiple teams are > > involved. In our deployment workflow we have separate teams taking > > care of dev. vs. production applications. > > > In order to push an app to production our Production team takes the > > application from the Development environment (once tested, QAed, etc.) > > and then pushes it out to production. They want to make sure that no > > one, except those that are supposed to, can touch production > > deployments. > > > In the scenario of having two apps under the same account, there is > > still the possibility that out of say 10 developers working on the > > application, one could mistakenly (or potentially on purpose) work > > with the wrong application. Maybe there are more knobs and switches > > there for access control which I haven't explored? > > > Also, we would like to separate costs between what our production > > environment is using and what our development environment is using. > > I'm not very clear if this information is readily available. Since > > we're still in our free quota I'm not clear on how this is can be > > accomplished either and separate accounts would also help... > > > Dre > > > On Jul 29, 4:20 pm, Roberto Saccon <[email protected]> wrote: > > > > maybe I am missing your point, but you can publish your app with two > > > different applications, stable versions two one app-ID, unstable ones > > > with another app-ID. Then you map the stable app towww.example.com > > > and the unstable one to dev.example.com > > > > -- > > > Roberto > > > > On Jul 28, 7:00 pm, Dre <[email protected]> wrote: > > > > > Hi, > > > > > I would like to separate out our dev and production accounts for App > > > > Engine so that developers can safely use the dev account without > > > > affecting production. For each account I would like to have well known > > > > names for the applications under the same domain. For instance: > > > > > dev account -> dev.example.com > > > > production account ->www.example.com > > > > > To create these CNAMEs I need to register the domain under the same > > > > account in Google Apps. However, I can't seem to register the same > > > > domain under two different accounts so I cannot set this scenario up. > > > > > Is there any way to get around the requirement of using Google Apps to > > > > register the domain? Not sure why I need to prove I own the domain if > > > > I have the power to setup the CNAMEs with my DNS provider anyway. > > > > > Maybe there is another accepted workflow on how to separate dev. and > > > > production environments? > > > > > Thanks, > > > > > Dre -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
