I agree with Philip! For someone who has lots of users/projects to manage in Engine, it just makes no more sense.
My personal "problem" was way simpler than that. I just wanted an e-mail host for my domain but I liked very much the interface by google of managing domain, my own (and oly) user along with all the resources, like Google Drive, calendar, contacts, tasks, etc all integrated... also with my android device. I have a domain at Namecheap whose e-mail host is OX. Their service is very good, but there is no integration with contacts and calendar and all the cloud advantages. I just was looking for the best way to have my tools and everything somehow sincronized. Cheers André 2015-01-22 8:08 GMT-02:00 Philip Kilner <[email protected]>: > Hi Vinny, > > On 22/01/15 04:22, Vinny P wrote: > >> You're talking about the difference between adding the domain as a >> secondary domain/adding it as an alias domain, correct? >> >> > Yes, I think so - don't recall the term "secondary, but looking at a paid > Google apps account, the option is described as: - > > "Add another domain > Manage users and groups at an associated domain that you own, > independently of the primary domain." > > ...so I think we're talking about the same thing. > > To connect a domain name to App Engine, it's always been recommended to >> use the domain as a primary or an alias domain on Apps. Configuring it >> as a secondary domain might give you distinct email accounts, but in my >> experience that introduces strange issues for Apps management and config >> - not only for App Engine but other services as well. I understand your >> point, but at the same time I think the change helps streamline Apps and >> probably helps reduce support costs as well. Frankly, I've always >> thought it was strange that Apps had 3 different ways (primary, >> secondary, alias) of configuring domains. >> >> > Re. problems, I haven't experienced those, but to be honest that's > probably because I'm not doing anything very complicated. > > Re. "helps streamline Apps and probably helps reduce support costs", I > don't honestly see that - this change makes the "grandafathered" free > versions different from the standard version in functionality as opposed to > numerical limits (which is surely /less/ streamlined), and given that were > are talking about the unpaid versions I don't supposed an enormous amount > of resource goes into support. > > FWIW, although Google have been silent on this issue, there is some > suggestion in the support forums that this was done to prevent abuse, > specifically to prevent people "selling" free apps accounts and using this > mechanism to switch domains. If that's the case, I'm a little perplexed - > seems like a crude way of combating the problem, and it seems like a > problem that is self-limiting in the sense that there can only be a finite > no. of these account out there. More to the point, I feel as though I'm > being punished for someone else's misbehaviour, and that Google haven't > been entirely straight about the fact, the timing, or the rationale for the > change. > > It might seem churlish complaining about tweaks to a free service, and I > absolutely do appreciate the fantastic freebie that apps for domains was > (and continues to be, up to a point), but it does constitute a change when > we were told the service would be unchanged, and it does make my existing > accounts much less useful for my purpose, in part because this has > diminished my confidence in continuity of service. > > If you absolutely must have free email accounts, I would suggest looking >> at your registrar - GoDaddy and other registrars occasionally have sales >> where they bundle free email or another service with the purchase of a >> domain. It's entirely possible to configure an alias domain, use it for >> an App Engine site, but to use an external mail service for that domain. >> >> > Sure - I run a bunch of servers with Virtualmin on them, so giving people > the ability to create multiple email addresses is not an issue. > > For me the issue is that I was able to set up projects with a domain name, > probably only two or three users (one of them me), and hand it over the > user as a coherent whole, where the Google Apps account let them manage > their domain, email, apps and - in some cases - App Engine apps with a > single account. > > Knitting together multiple services is fiddly for me, and the result is > messier for my users. What I've come to realise is that the Google account > within the Apps domain was the valuable bit - without that, its easier to > host and deploy elsewhere. > > Having said all the above, I recognise that I'm probably not that great a > fit for App Engine, and that this change has just made that clear to me - > my point is merely that this is an unannounced change to the service, and > that for some of us it means that these grandfathered accounts are no > longer useful for new projects. > > > -- > > Regards, > > PhilK > > > 'a bell is a cup...until it is struck' > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google App Engine" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/google-appengine/pVZfdeky-ow/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/google-appengine. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/google-appengine/54C0CC12.7040909%40gmail.com. > > For more options, visit https://groups.google.com/d/optout. > -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAFbOS96UcP4tEc78MctHr2f48MNqE58W4hGa1bWO_fPLk5bejw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
