Skip to main content

Google Apps and the Wonder that they are

Generally I've used Google Apps for mail and shared calendars and little else. I have, however, been asked to play with them to host a website and I've found them to be truly excellent in what they can do. Firstly a few tips:

  • If you want your www.yourdomain.com to point to your Google Apps site, make sure you set up the "sites" page to something like sites.yourdomain.com and then create your Google site and point it to www. via DNS. A CNAME DNS entry will take care of this.
  • Make sure your DNS is nice and tidy for all of this to work properly.
  • When creating your site, if it's the site for everyone to reach don't forget to make it public.
There is a great range of templates and options for configuring your webpage and I urge you to play with them all. I've found many amazing different options for working with the site and the ability to easily use Google Maps and embed other things like shared calendars is terrific.

I've also found the response times from the Google App servers to be less than what they advertise. Today it was indicated it would take up to 3 hours for a change to complete and it was done in about 20 minutes. 

The email and calendar aspects of Google Apps are excellent, much like the Gmail offering from Google. I have a lot of documents floating around my Apps account and find that sharing this info with my wife works brilliantly. She is relatively tech literate and that makes it even easier. I've found with some of my clients who are not technical in any way, that Google Apps are intuitive and easy for them to work with. The interface is clean and very usable with being intimidating.

About the only gripe I have is that I like to have my Gmail and Apps accounts open at the same time in the same browser and it doesn't like that. Perhaps its more my work process there than Apps so I don't hold it against them.

Comments

Popular posts from this blog

Plone - the open source Content Management System - a review

One of my clients, a non-profit, has a lot of files on it's clients. They need a way to digitally store these files, securely and with availability for certain people. They also need these files to expire and be deleted after a given length of time - usually about 7 years. These were the parameters I was given to search for a Document Management System (DMS) or more commonly a Content Management System (CMS). There are quite a lot of them, but most are designed for front facing information delivery - that is, to write something, put it up for review, have it reviewed and then published. We do not want this data published ever - and some CMS's make that a bit tricky to manage. So at the end of the day, I looked into several CMS systems that looked like they could be useful. The first one to be reviewed was OpenKM ( www.openkm.com ). It looked OK, was open source which is preferable and seemed to have solid security and publishing options. Backing up the database and upgradin

Musings on System Administration

I was reading an article discussing forensic preparation for computer systems. Some of the stuff in there I knew the general theory of, but not the specifics of how to perform. As I thought about it, it occurred to me that Systems Administration is such a vast field. There is no way I can know all of this stuff. I made a list of the software and operating systems I currently manage. They include: - Windows Server 2003, Standard and Enterprise - Exchange 2003 - Windows XP - Windows Vista - Windows 2000 - Ubuntu Linux - OpenSuSE Linux - Mac OSX (10.3 and 10.4) - Solaris 8 - SQL 2005 - Various specialised software for the transport industry I have specific knowledge on some of this, broad knowledge on all of it, and always think "There's so much I *don't* know". It gets a bit down heartening sometimes. For one thing - I have no clue about SQL 2005 and I need to make it work with another bit of software. All complicated and nothing straightforward. Irritating doesn&

Traffic Monitoring using Ubuntu Linux, ntop, iftop and bridging

This is an update of an older post, as the utilities change, so has this concept of a cheap network spike - I use it to troubleshoot network issues, usually between a router and the network to understand what traffic is going where. The concept involves a transparent bridge between two network interface cards, and then looking at that traffic with a variety of tools to determine network traffic specifics. Most recently I used one to determine if a 4MB SDSL connection was saturated or not. It turned out the router was incorrectly configured and the connection had a maximum usage under 100Kb/s (!) At $1600 / month it's probably important to get this right - especially when the client was considering upgrading to a faster (and more expensive) link based on their DSL provider's advice. Hardware requirements: I'm using an old Dell Vostro desktop PC with a dual gigabit NIC in it - low profile and fits into the box nicely. Added a bit of extra RAM and a decent disk and that&