3 ms·
AppEngine is (especially) nice for hobby projects fitting into the free quota. Although the concept is generally great, for commercial use there are some frustr
by Yaggo 16y ago
AppEngine is (especially) nice for hobby projects fitting into the free quota. Although the concept is generally great, for commercial use there are some frustrating restrictions, such as lack of support for naked domains, which nailed my decision to go with Tornado + MongoDB + <your-favorite-cloud-hosting>.
- olifante 16y agoWhat do you mean by lack of support for naked domains? You can host your AppEngine app at yourdomain.com via Google Apps, as described here: http://code.google.com/appengine/docs/domain.html http://code.google.com/appengine/docs/domain.html I haven't heard of any limitations on using custom domains for commercial use, cf. http://groups.google.com/group/google-appengine/browse_thread/thread/4e1299bda9341b07 http://groups.google.com/group/google-appengine/browse_threa...
- Yaggo 16y ago> Due to recent changes, App Engine no longer supports mapping your app to a naked domain. If your domain registrar supports URL redirects, you can redirect from http://yourdomain.com http://yourdomain.com to e.g http://www.yourdomain.com http://www.yourdomain.com or http://appid.yourdomain.com http://appid.yourdomain.com. http://code.google.com/appengine/kb/general.html#naked_domain http://code.google.com/appengine/kb/general.html#naked_domai... http://stackoverflow.com/questions/817809/how-to-use-google-app-engine-with-my-own-domain-not-subdomain http://stackoverflow.com/questions/817809/how-to-use-google-... http://blog.notdot.net/2009/12/Naked-domains-on-App-Engine http://blog.notdot.net/2009/12/Naked-domains-on-App-Engine (For non-commercial use this limitation may be more acceptable, but if you are seriously launching a commercial service, you probably want to freely choose your domain.)