Chrome Tip: Multi-profiles and Offline Docs

You may have already used the Chrome incognito profile, but what you may not know about is the fact that chrome now allows you to create and use multiple profiles on your computer. While incognito us used to specfically ensure that no data is stored or tracked on your system based on the sites and pages you visit, profiles allow you to better manage the various ways those pages are stored either online or off. Here is how to use them.

Incognito Mode:

Incognito mode ( i.e. the mode with the browser icon as a sunglass and hat wearing fellow in this blog’s screen shot ) prevents pages you visit from being tracked, stored in history and clears all cookies from your session once the window is closed, no matter what the site you are visiting has set. There are many reasons why you may want to do this. The cite version: You and your girlfriend use the same computer and you don’t want her to know about the surprise earrings you have been shopping for her online. The not so cute version, well, let’s just say you can avoid getting in trouble like Jim Levenstein does in American Reunion. (BTW, that movie is not worth seeing even if to only get the joke)

To enable incognito mode go to the menu ( ) option in the top right corner of your Chrome browser and select “New Incognito Window” or press Command+Shift+N . Also note: Chrome in your app on your mobile device has the same options and works the same way.

Signing in to Chrome

Chrome can connect to your GMail account, and doing so allows you to do things like sync bookmarks between devices, as well as allow you to edit your Google Drive documents stored on the cloud even while you have no internet connection available. This tool came in handy recently when I came up with some ideas for a document I was working on while at a hotel that didn’t have wifi available. I simply made the changes needed and when internet resumed the doc was synced and merged to my online version of the doc. By signing in to your Google account on chrome a default profile for your computer ( i.e. the mode with the browser icon as a head with no face in this blog’s screen shot ) will be automatically assigned to you and connected to the account you signed in with.

To login to your Google account in Chrome go to the menu ( ) option in the top right corner of your Chrome browser and select “Sign In”. You will then be given the Google login page. Sign in as you would with your GMail account and you are all set.

Enabling Your Chrome Profile to Work on Docs Offline

If you haven’t used your Google Drive already you should really take a second to get to know it. Not only can you store 5GB of files of any type for free in your Google Drive AND use them as a local drive on your computer and phone just like Dropbox, BUT you can use it to create and save documents of various types that you can use to collaborate on simultaneous with other users.

To explain the latter more clearly through example: We use Google Docs at Socialize at all our meetings. During the meeting we create a google doc and throughout the meeting anyone can add, append, change or update the way the notes are taken all at the same time. You can see one another typing as you type and often times most of the meeting will be completed in silence while everyone adds their notes to the doc. Collaboration is saved and shared in a document instantly.

But I digress…

To enable your Google docs to have offline access first go to your Google Drive (http://drive.google.com). On the left hand menu select the “more” drop down to reveal extra options. Finally click “offline docs” and enable. Your drive will sync your docs to your local Chrome profile. Note: If you do not see the “Offline Docs” in the “more” dropdown, and you are using Google App for work, you will need to either enable the feature in your Google App’s Admin portal, or get your sysadmin to do it for you. It is located in the Google Drive sectionof the Admin’s “Settings” tab.

Multiple Chrome Profiles

You are probably just fine getting your Google Drive working on your default Chrome profile to work on offline docs, just as I was for quite some time. The problem is that when I tried to enable offline docs for my personal Google Drive documents, as well as my work docs, the Google Drive system did not allow it. Chrome only allows one offline sync per Chrome profile. To fix this problem you will need to create an additional Chrome Profile on your browser ( i.e. create a mode with a different browser icon like the one with the Ninja in this blog’s screen shot ), and then enable Offline Docs in your Google Drive while in the correct profile.

To add additional profiles to Chrome go to the menu ( ) option in the top right corner of your Chrome browser and select “Settings”. Scroll down to the “Users” section and choose “Add new user.” Once you have added a profile correctly your Users section should look something like this:

Switching Between Profiles

To switch between profile simply click the icon for your current profile in the top right of the browser and choose the profile you wish to use. Once selected, a new browser window will open with that profile enabled.

Leave the caves and create your tools!

GAE offers a free to get started approach, along with an instant “hello word” initial environment, making sandboxing ideas and building helpful tools for productivuty a snap.

To get started, download GAE, press the plus sign in the bottom left corner. Set the directory you would like to work out of and your almost done. Well, at least you are already at the stage you need to be to start playing with the system locally, in what we call the development environment (No one can see your system but you.) Just hit the [play] button on the GAE dashboard and you are running with your first environment. Just click the Browser (the compass looking thing), or go to http://localhost:8080 in your browser, and you should see your first “hello word! It is quite reassuring to see it work so smoothly (if indeed it does), and if this is the first time you have coded, trust me they have taken out a hell of allot of pain out of the tedium it can take to get here.

Without getting into the nitty gritty of code just yet, let’s push your baby to production (That means make it live/accessible to the world). That’s right, you are about to push a web application live to production!  First create a new app at the google app engine home page and follow the steps there (setting up your yaml for upload). Your yaml file tells google which app your are updating when you do so. Not making sure your yaml matches your project is like  you sending mail through the USPS without out a “from”/”to” address.

Once complete, press the blue arrow pointing upward (the “deploy” button) and it will deploy (AKA: push to prod, go live.)

Once deployed, you can update, monitor, or even share you application with the world. And all for free. Not that this baby would get allot of attention in its current state (just a “hello world”), but if it did, it would also be scalable. I mean 10 years ago this would have cost you quite a bit of time money, especially if you didnt know allot about server configurations, apache, linux, or windows server, or…well you get the idea.

There are a few sample apps you can play with on the GAE site. If you are ready, start developing some code i Python. Maybe had a hellow world message of your own.

When you start feeling saucy, try and create a model. A model is a data structure you can save, or persist, data to your system. Again to you newbies out there, this is the equivelent of your granfather telling you, “back in my day I had to walk up a hill in the snow to get to work, and up a hill in a blizzard to get back.” Setting up a database on a production server was a skill on its own, but to create one that is scalable, and without the need to architect it is amazing. You see, based on the models you create GAE intuitivley creates your “database”, stores it efficiently, and assumes where indexes need to be placed. You really don’t have to understand any of this, but if you want to you can look up those terms have at it: indexing, database, architecture, MVC…. Like I said, I’m just an old guy complaining about hills.

If you are still a bit timid about getting started, don’t worry there is a baby step in between these tween sized steps that can help you get ramped up before you start churning out lines and lines of code. Click on the “SDK Console” button on the GAE dashboard. It will open up a web page that is running locally, on your stage environment, that gives you windows into your system to hack around with. (This console lives inside your development app, so don’t forget to run your new app to get access to it.) Once in the console, click “Interactive Console”. There you will have a very rudimentary terminal that you can write temporary test scripts in. The output is shown on the right of the screen. This is a great place to get errors, make mistakes, and go nuts! (Note: The SDK Console also houses your development DB, so you can check to see what data you are saving after you have attempted to save it.)

Note: The easiest way to get started as a newbie, in my mind, is by using Python in GAE. Java, although awesome, is a bit more advanced.

I recently used GAE to create a few projects to help out the team. One for TeamCity monitor to view coverage reports and if a build is broken or not. And also one for Pivatol Tracker to help our press and marketing interpret what is coming out of the product pipeline, if its ready, and what are the stories of value within. I will post templates for those projects in the near future.