Skip to main content

How to create a Professtional Free Website with Google Apps

GAE hosting is available for Everyone. (Is this the end of hosting providers?) This is very welcome for all those people who have an ambition to put a free website with no adgood features, reliabilty and scalabity.

For Starters,
- you have to know or learn python (it is the only language supported on GAE right now) or just get started
- If you want your own domain name, You have to have one or you have to understand DNS, subdomains, CNAMEs, ANAMEs, MX records.

- Create an app in GAE (I will skip the whole tutorial on how to do it)
- Create a domain (buy it from a domain hosting service like godaddy - always keep hosting and domains in seperate places for better control)
- Create a Google Apps Account (Again I will skip the whole tutorial).
- Verify your ownership of the domain and connect it to google App
- Modify DNS MX Entries, set up your email.
- Create Custom urls for services (calendar, docs, etc) with custom sub domains urls.
- Add your GAE app in Google App Admin Dashboard (add services)
- Define Custom urls by adding them to this app.
- If you have a blog, make a custom subdomain for that too.

Thats it, you have a free website, with email and calendar and docs.

More updates with screenshots and more detailed instructions soon so stay tuned.

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>