<commit_before>![Travis Build Status](https://travis-ci.org/GoogleCloudPlatform/gcloud-node.svg)

Work in progress... Watch the repo for notifications.
<commit_msg>Adding the quick start docs.<commit_after># Google Cloud Node.js Client

Node idiomatic client for Google Cloud services. Work in progress... Watch the repo for notifications.

![Travis Build Status](https://travis-ci.org/GoogleCloudPlatform/gcloud-node.svg)

This client support the following Google Cloud services:

* [Google Cloud Datastore](https://developers.google.com/datastore/) (externalized Megastore, also allows access to the collections of existing AppEngine apps)
* [Google Cloud Storage](https://cloud.google.com/products/cloud-storage/)
* Planned but not yet started: [Google Compute Engine](https://developers.google.com/compute), and [Google BigQuery](https://developers.google.com/bigquery/)

## Quickstart

~~~~
npm install gcloud
~~~~

### On Google Compute Engine

If you are running this client on Google Compute Engine, you can skip to the developer's guide. We handle authorization for you with no configuration.

### Elsewhere

If you are not running it on a Google Compute Engine VM, you need a Google Developers service account. To create a service account:

* Visit the [Google Developers Console](https://console.developers.google.com/project).
* Create a new project or click on an existing project.
* Enable billing if you haven't already.
* On the "APIs & auth" tab, click APIs section and turn on the following. You may need to enable billing in order to use these services.
	* Google Cloud Datastore API
	* Google Cloud Storage
	* Google Cloud Storage JSON API
* Once API access is enabled, switch back to "APIs & auth" section on the navigation panel and switch to "Credentials" page.
* Click on "Create new client ID" to create a new **service account**. Once the account is created, a p12 file will be auto downloaded. The downloaded file is the private key you'll need for authorization.
* You'll the following for auth configuration:
	* Developers Console project's ID (e.g. bamboo-shift-455)
	* Service account's email address (e.g. <EMAIL>)
	* The path to the downloaded private key.
	
## Developer's Guide

TODO

## Contributing

Fork the repo, make changes and open a pull request.

* `npm test` to run tests.
* `npm run cover` to see the test coverage report.

Before we can accept any pull requests
we have to jump through a couple of legal hurdles,
primarily a Contributor License Agreement (CLA):

- **If you are an individual writing original source code**
  and you're sure you own the intellectual property,
  then you'll need to sign an [individual CLA](http://code.google.com/legal/individual-cla-v1.0.html).
- **If you work for a company that wants to allow you to contribute your work**,
  then you'll need to sign a [corporate CLA](http://code.google.com/legal/corporate-cla-v1.0.html).

You can sign these electronically (just scroll to the bottom).
After that, we'll be able to accept your pull requests.

{'fraction_non_alphanumeric': 0.08721506442021804, 'fraction_numerical': 0.002973240832507433, 'mean_word_length': 4.416815742397138, 'pattern_counts': {'":': 0, '<': 4, '<?xml version=': 0, '>': 4, 'https://': 7, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 7, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5841425', 'n_tokens_mistral': 842, 'n_tokens_neox': 797, 'n_words': 390}