views:

1981

answers:

4

I've been fooling around with the Google App Engine for a few days and I have a little hobby application that I want to write and deploy.

However I'd like to set it up so that users are not directly accessing the app via appspot.com.

Is hosting it through Google Apps and then pointing it at my own domain the only way to go? I looked at that a little bit and it seemed like a pain to implement but maybe I'm just missing something.

My other thought was to write the app-engine piece as a more generic web-service.

Then I could have the user-facing piece be hosted anywhere, written in any language, and have it query the appspot.com url.

Anyone have any luck with the web-service approach?

+6  A: 

To do this, I believe you need to be using Google Apps and have a custom domain setup for Google Apps. Then, you deploy your app into your Google Apps domain.

Joe Skora
Hurmmm...I'd love to not have to use Google Apps. It'll be interesting to see if anyone has had usuccess with other approaches.
Mark Biek
It doesn't appear to be optional based on the "deploy your app" link above.
Joe Skora
You don't have to use Google Apps, right? Sign up and don't use any of its services.
ceejayoz
I've edited the question to try and clarify my intent a bit.
Mark Biek
I still don't see the objection. It's free, and you can use it solely for mapping App Engine apps to domains if you want.
Nick Johnson
A: 

Can you clarify why it is you don't want to use Google Apps? It doesn't cost anything, and as others have pointed out, you don't have to use any of the services. If you already have a google apps domain, you can just add this one as an alias and map it to the App Engine app, too.

Nick Johnson
It just seemed like an extra layer of complexity that would nice to avoid (if possible). Maybe I'm just being to picky about the choices presented by a free service.
Mark Biek
Google Apps is NOT free, it costs $50 per user per year.
PropellerHead
Standard Edition is free: http://www.google.com/apps/intl/en/group/index.html - and that's all you need in order to map a domain to an App Engine app.
Nick Johnson
+1  A: 

The reason Google Apps is required is because you need somewhere to a) verify you own the domain (otherwise, you might point it at app engine, then I might hijack it by adding it to my account) and b) set up domain mappings (which subdomains point to which of your appengine apps).

Since this stuff already exists in Apps, it seems silly to duplicate it in AppEngine.

As has been pointed out, it doesn't cost anything, and you do not need to "move" anything to Google. You simple created a cname record with a random name to verify you own the domain, and a cname for the subdomain you wish to point at App Engine. This only takes a few minutes, and once it's done, it's done forever.

Note: If you host your site elsewhere and use webservices, you need to scale the site/frontend. If you host on app engine, you get this for free :-)

I wrote an article on my blog about redirecting *.appspot.com domains to your custom domain to keep your branding:

http://blog.dantup.com/2009/12/redirecting-requests-from-appid-appspot-com-to-a-custom-domain

Danny Tuppeny
+1 for providing an explanation *why* Google Apps usage is actually required, despite question hasn't been active for a couple of month.
Steffen Opel
+1  A: 

Here is google's official instructions on how to do that:

http://code.google.com/appengine/docs/domain.html

I have used this process for a couple of sites and it is easy and painless, provided you have control on the DNS records for your domain (you should).

Cleber Goncalves