Quota limits for domains

[Pablo `el Guapo` Borges]

Hey there,

I'm just wondering, is there a fixed quota limit on how many domains I
could have associated with my app ?

Thanks in advance,

[Jeff S]

Hi Pablo,

I'm not aware of any limits on the number of domains you can associate
with your app. Are you restricting login to accounts in a specific set
of domains? If so, it is a good idea to give your app an address in
all of the allowed domains. For example, if you gave access to only
users in example.com, you would want to make sure your app has an
example.com address.

Thank you,

Jeff

On Aug 4, 11:57 pm, "Pablo `el Guapo` Borges" <pabl...@gmail.com>
wrote:

[Pablo `el Guapo` Borges]

Thanks for the input, Jeff, but actually I'm concerned about first
party cookies.

I want to be able to let my users point to my App on GAE (say
app.theirdomain.com CNAME ghs.google.com) and store a few cookies on
their domain, hence the concern about how many domains I could
associate with my app. :)

Cheers,

[DocDay]

The answer appears to be, unfortunately, exactly:

ONE
!!!

For instance, example.com and www.example.com are allowed, but
adding another, such as example1.com or even example.net are
stubbornly refused.

Whenever GAE docs and dashboard refer to "new URL", they're
talking about THIRD-LEVEL and higher URL on the SAME
second-level domain. For instance, test.example.com or
pablo.example.com.

Disallowing multiple second-level domains aliased to a single
GAE app seems to be "by design". Two points:

1) For some details, see this discussion:
http://groups.google.com/group/google-appengine/browse_thread/thread/b2ef9b72533f11e1/15be1796b8472f23?hl=en

2) Ask GAE to support multiple second-level domain aliases. To do so,
please visit and "star" this issue:

Issue 638: Google Apps domain alias won't work in Google App
Engine
http://code.google.com/p/googleappengine/issues/detail?id=638

DocDay




On Aug 7, 11:06 pm, "Pablo `el Guapo` Borges" <pabl...@gmail.com>
wrote:

> Thanks for the input, Jeff, but actually I'm concerned about first
> party cookies.
>
> I want to be able to let my users point to my App on GAE (say
> app.theirdomain.com CNAME ghs.google.com) and store a few cookies on

> theirdomain, hence the concern about how many domains I could

> associate with my app. :)
>
> Cheers,
>
> On Aug 6, 5:07 pm, Jeff S <j...@google.com> wrote:
>
>
>
> > Hi Pablo,
>
> > I'm not aware of any limits on the number of domains you can associate
> > with your app. Are you restricting login to accounts in a specific set
> > of domains? If so, it is a good idea to give your app an address in
> > all of the allowed domains. For example, if you gave access to only
> > users in example.com, you would want to make sure your app has an
> > example.com address.
>
> > Thank you,
>
> > Jeff
>
> > On Aug 4, 11:57 pm, "Pablo `el Guapo` Borges" <pabl...@gmail.com>
> > wrote:
>
> > > Hey there,
>
> > > I'm just wondering, is there a fixed quota limit on how many domains I
> > > could have associated with my app ?
>

> > > Thanks in advance,- Hide quoted text -
>
> - Show quoted text -

[Bryan Pendleton]

Actually, if the users you want to enable to add your domain have GAppsForDomains accounts, *they* can put in the alias themselves, by adding your AppEngine identifier as a new GAE instance associated with their domain (and updating DNS, if necessary). I just tried this with an app from the appspot gallery, and it worked fine.

This is probably a lot more steps than you'd like for the average user, but it is possible, nonetheless. 
--
Bryan A. P. Pendleton

[Pablo `el Guapo` Borges]

That's a major show-stopper for me. :(

Guess I can't keep on using GAE for my project after all. :)

On Aug 16, 7:56 pm, DocDay <Google....@eoasys.com> wrote:
> The answer appears to be, unfortunately, exactly:
>
>       ONE
>       !!!
>

> For instance, example.com andwww.example.comare allowed, but

> adding another, such as example1.com or even example.net are
> stubbornly refused.
>
> Whenever GAE docs and dashboard refer to "new URL", they're
> talking about THIRD-LEVEL and higher URL on the SAME
> second-level domain. For instance, test.example.com or
> pablo.example.com.
>

> Disallowing multiple second-leveldomainsaliased to a single

> GAE app seems to be "by design". Two points:
>
> 1) For some details, see this discussion:

>    http://groups.google.com/group/google-appengine/browse_thread/thread/...

>
> 2) Ask GAE to support multiple second-level domain aliases. To do so,
>    please visit and "star" this issue:
>
>    Issue 638: Google Apps domain alias won't work in Google App
> Engine
>      http://code.google.com/p/googleappengine/issues/detail?id=638
>
> DocDay
>
> On Aug 7, 11:06 pm, "Pablo `el Guapo` Borges" <pabl...@gmail.com>
> wrote:
>
> > Thanks for the input, Jeff, but actually I'm concerned about first
> > party cookies.
>
> > I want to be able to let my users point to my App on GAE (say
> > app.theirdomain.com CNAME ghs.google.com) and store a few cookies on

> > theirdomain, hence the concern about how manydomainsI could

> > associate with my app. :)
>
> > Cheers,
>
> > On Aug 6, 5:07 pm, Jeff S <j...@google.com> wrote:
>
> > > Hi Pablo,
>

> > > I'm not aware of any limits on the number ofdomainsyou can associate

> > > with your app. Are you restricting login to accounts in a specific set

> > > ofdomains? If so, it is a good idea to give your app an address in
> > > all of the alloweddomains. For example, if you gave access to only

[Harlley Roberto]

I think GAE is not ready to production apps.

=================
Harlley R. Oliveira
www.webtoo.com.br
=================