why make adding a domain so difficult?
Locke
use www.domain.com with appid.appspot.com, then why the heck can't I
simply prove my ownership by setting the CNAME appid-
owner.www.domain.com then pointing www.domin.com to ghs.google.com?
Why make me jump through all the hoops with Google Apps, a service I
have no intention of using?
KISS!
/me sees "Sorry, you've reached a login page for a domain that isn't
using Google Apps" again and bangs his head against the keyboard
nmsxzdwccfdxcsfsddxcsfvxfvdxcv
Nickolas Daskalou
simplified.
On Dec 21, 9:42 am, Locke <locke2...@gmail.com> wrote:
> If I own the appid "appid" and the domin "domian.com" and I want to
> usewww.domain.comwith appid.appspot.com, then why the heck can't I
> simply prove my ownership by setting the CNAME appid-
> owner.www.domain.comthen pointingwww.domin.comto ghs.google.com?
Gerard Mason
groups.google.com/group/google-appengine/browse_thread/thread/
26eaaad8610842c8/508ab7affceeee01?lnk=gst&q=gerard
+mason#508ab7affceeee01). The documentation isn't very clear and whole
process could be much simpler. It looks like there's a rogue marketer
loose amongst the Google engineers, who's intent on using App Engine
to boost usage of Google Apps.
If you have ten different applications, which you want to host on ten
different domains, then you end up creating ten different Google
accounts and installing Google Apps for ten different domains. In a
way it's completely ridiculous but, hey, at least it ensures that the
administrative emails don't get mixed up!
On Dec 20, 10:42 pm, Locke <locke2...@gmail.com> wrote:
> If I own the appid "appid" and the domin "domian.com" and I want to
> usewww.domain.comwith appid.appspot.com, then why the heck can't I
> simply prove my ownership by setting the CNAME appid-
> owner.www.domain.comthen pointingwww.domin.comto ghs.google.com?