Thanks James,
I may have gotten the wrong end of the stick here.
I've been playing around with the SDK up to now but have not actually
deployed yet.
Are you basically saying that I can...
1. Allow 1000s of Google Apps account holders to easily deploy
*isolated instances* of my app:
2. Protect my app code from inspection by said Google Apps account
holders.
3. Assign responsibility for hosting cost of app instances to said
Google Apps account holders (when the service is eventually monetised)
4. Roll-out software updates automatically to each Google Apps account
holder who uses my app.
If the answer is "YES" to each of the above, then you will have made
my day!!
On Dec 10, 6:28 pm, James Ashley <[EMAIL PROTECTED]> wrote:
> Maybe I'm missing something. But it doesn't seem like it would take
> much effort to write a script to automate it.
>
> Something along the lines of:
>
> instance_names = ('a', 'b', 'c',...)
>
> for name in instance_names:
> # change the instance name in app.yaml
>
> # call appcfg.py
>
> You'd probably want to keep the instance names in a database, to
> associate with billing, etc, but that could be something for later
> down the road.
>
> On Dec 10, 5:25 am, rvjcallanan <[EMAIL PROTECTED]> wrote:
>
> > I am new to GAE (who isn't?) and this subject has been touched on
> > before in a number of guises but I think we could all benefit from a
> > little more clarity.
>
> > I am developing a "proof-of-concept" business app which can benefit
> > hugely from the GAE framework. My ideal scenario is to deploy the app
> > to each customer as a separate isolated instance, integrated within
> > his managed Google Apps business account.
>
> > The main reasons for this preference are:
>
> > 1. I would like to keep customer data and bugs isolated
>
> > 2. Each customer is an island as far as the application data model is
> > concerned. One big database would require all tables and queries to be
> > qualified by a customer ID, adding an unnecessary layer of complexity
> > and impacting performance.
>
> > 3. I would like each customer to take individual responsibility for
> > hosting costs
>
> > 4. I wish to leverage the Google Apps for managing user accounts
> > within each organisation.
>
> > 5. I wish to expose my own API to allow for customisation.
>
> > Bear in mind that each app instance may have to support a few thousand
> > users at most (but probably not millions).
>
> > Right now, deploying individual app instances in the way described
> > above is kludgy at best. While it may be feasible to do this manually
> > for a small number of high-value customers, it is certainly not a
> > scalable solution. There is also the issue of protecting intellectual
> > property.
>
> > I am wondering if there is anything in the "unofficial" roadmap to
> > address this requirement in the future. I would like to start
> > developing now on the basis that deployment of individual app
> > instances (and updates) will eventually be a single-click operation.
>
> > Is this wishful thinking?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
