# Hermes Hermes offers several services not available in a Web Browser through one (or several) Node.js processes: * [Filesystem services](#filesystem-services) ([Local](#local-filesystem-service), [Dropbox](#dropbox-filesystem-service)) * [Project templates services](#project-template-services) * [Build Services](#build-services) ([PhoneGap Build](#phonegap-build-service), ...) ## Security[](id:security) ### Same-Origin Policy - CORS By default, Ares backend only allows requests from Ares itself, using built-in HTTP methods & headers. This is reflected in the default top-level `ide.json`: ``` "cors": { "origins": [], "methods": [] }, "headers": {}, ``` It is possible to hard-wire a new set of allowed origins (for example when running behind a Secure Reverse Proxy) using the `cors.origins:` Array property. It is possible to allow more methods using the `cors.methods:` Array (in addition to the REST verbs `GET`, `PUT`, `POST` and `DELETE` which are already allowed). It is also possible to hard-wire some HTTP headers using the `headers:` Object property, as shown below. The customized user-defined headers are automatically added to the built-in list of headers allowed by CORS. ``` "cors": { "origins": ["http://www.google.com"], "methods": ["DOTHIS", "DOTHAT"] }, "headers": { "X-My-Header": "My Value", "X-My-Other-Header": "My Other Value" }, ``` ### Authentication Each service may need an individual authentication to access a back-end in the cloud. For example, PhoneGap Build (PGB) uses a simple per-user token that is provided as a query parameter with every request to the build service. Another example is more complex example is Dropbox, which requires both an application OAuth token pair (for Ares itself), plus a per-user account (the one users use to access their private data on Dropbox). There are a variety of possible While authentications token are generally used by the Node.js-based Ares services (rather than by the Ares client application runnin in the Browser), the server server stores them locally: they ares stored in the Browser sandbox (cookies, localStorage... etc) and passed to the service when needed. The elements of the authentication token that are tight to the server (rather than to the end-user) are set on the server in the `"auth":{...}` of `ide.json`, for each service. This section is saved under `localStorage` key `com.hp.ares.services..auth` in the Browser. The value associated with this key expands as the user feeds necessary credentails to each service. The actual properties stored within each `"auth":{...}` are essentially service-specific. **NOTE:** The `localStorage` values are not encrypted. This could be changed if proven to be useful. ### Phonegap Build Account A user can be authentified in a Phonegap account in two possible ways : - Using and **Adobe ID**: the Adobe account (login+password) - Using a **Github ID** : the Github account (login+password) In order to run the Phonegap build service from Ares, the authentication must be done with the Adobe ID. So if the user has registered on the Phonegap account using Github account, these steps must be followed: 1. Click on the upper right profile icon and select *Edit account* 2. In the tab *Account details* click on *Connect an Adobe ID* 3. If you have already an Adobe account, just use it to sign in otherwise, Click on the button *Create Adobe ID* to register for a new Adobe account. 4. Now you can use the Adobe ID to connect to the Phonegap account in Ares. **NOTE**: - Due to a certain restriction on the edition of the Adobe account, a user can't change the linked Adobe ID on his Phonegap account. - A user can unlink his Phonegap account from the Github account by following these steps: 1. The user must be authenticated in Github 2. Open this page https://github.com/settings/applications 3. In the section *Authorized applications* click on *Revoke* button of the row *Phonegap:Build*. ## Filesystem services[](id:filesystem-services) ### Protocol #### Resources * `/id/{id}` resources are accessible via avery verbs described below. These resources are used to browse the folder tree & get idividual items * `/file/*` resources are files that are known to exist. These resources are used by the Enyo Javascript parser & by the Ares _Project Preview_ feature. They can only be accessed using `GET`. #### Verbs Hermes file-system providers use verbs that closely mimic the semantics defined by [WebDAV (RFC4918)](http://tools.ietf.org/html/rfc4918): although Hermes reuses the same HTTP verbs (`GET`, `PUT`, `PROPFIND`, `MKCOL`, `DELETE` ...), it differs in terms of carried data. Many (if not most) of the HTTP clients implement only the `GET` and `POST` HTTP verbs: Hermes uses [X-HTTP-Method-Overrides](http://fandry.blogspot.fr/2012/03/x-http-header-method-override-and-rest.html) as WebDAV usually does. As a potential security hole (enforced by Express), Ares does **not** support the special `_method` query parameter . * `PROPFIND` lists properties of a resource. It recurses into the collections according to the `depth` parameter, which may be 0, 1, ... etc plus `infinity`. For example, the following directory structure: $ tree dir1/ dir1/ |-- file0 |-- file1 ... corresponds to the following JSON object (multi-level node descriptor) returned by `PROPFIND`. The node descriptor Object format is defined by [this JSON schema](../assets/schema/com.enyojs.ares.fs.node.schema.json). The `path` property is node location absolute to the Hermes file-system server root: it uses URL notation: UNIX-type folder separator (`/`), not Windows-like (`\\`). $ curl "http://127.0.0.1:9009/id/%2F?_method=PROPFIND&depth=10" { "isDir": true, "path": "/", "name": "", "children": [ { "isDir": true, "path": "/dir1", "name": "dir1", "id": "12efa4560" "children": [ { "isDir": false, "path": "/dir1/file0", "name": "file0", "id": "12efab780" }, { "isDir": false, "path": "/dir1/file1", "name": "file1", "id": "0ae12ef56" } ] }, ], "id": "934789346956340", "versionTag": "af34ef45", } * `MKCOL` create a collection (a folder) into the given collection, as `name` passed as a query parameter (and therefore URL-encoded). When the `overwrite` parameter is explicitly set to `"false"` (as a string), `MKCOL` may fails with an HTTP status code `412/Resource Already Exists`. It returns a JSON-encoded single-level (depth=0) node descriptor of the new folder. $ curl -d "" "http://127.0.0.1:9009/id/%2F?_method=MKCOL&name=tata" * `GET` can be used: * ***`On files:`*** to get the content of a particular file. The optional query parameter `versionTag` comes from a previous call to `GET` on the same file. The HTTP header `x-ares-node` (lowecase) contains a JSON-encoded version of the file's node descriptor (the one returned by `PROPFIND` for this file). * ***`On folders:`*** to get the content of all the files of the folder encoded in base64 into a single FormData. An additional query parameter "format" set to "base64" is expected. An error will be returned if this "format" query parameter is not present or is not equal to "base64". Other encoding may be added later on. * `PUT` creates or overwrite one or more file resources, provided as `application/x-www-form-urlencoded` or `multipart/form-data`. It returns a JSON-encoded array of single-level (depth=0) node descriptors for each uploaded files. When the `overwrite` parameter is explicitly set to `"false"` (as a string), `PUT` may fails with an HTTP status code `412/Resource Already Exists`. * `application/x-www-form-urlencoded` contains a single base64-encoded file in the form field named `content`. The file name and location are provided by `{id}` and optionally `name` query parameter. * `multipart/form-data` follows the standard format. For each file `filename` is interpreted relativelly to the folder `{id}` provided in the URL. **Note:** To accomodate an issue with old Firefox releases (eg. Firefox 10), fields labelled `filename` overwrite the `filename` in their corresponding `file` fields. See `fsBase#_putMultipart()` for more details. * `DELETE` delete a resource (a file), which might be a collection (a folder). Status codes: * `200/OK` success, resource successfully removed. The method returns the new node descriptor (as `PROPFIND` would return) of the parent of the deleted resource. $ curl -d "" "http://127.0.0.1:9009/id/%2Ftata?_method=DELETE" * `COPY` reccursively copies a resource as a new `name` or `folderId` provided in the query string (one of them is required, only one is taken into account, `name` takes precedence if both are provided in the query-string). The optionnal query parameter `overwrite` defines whether the `COPY` should try to overwrite an existing resource or not (default value: `"true"`). The method returns the node descriptor (as `PROPFIND` would return) of the new resource. * `201/Created` success, a new resource is created * `200/Ok` success, an existing resource was successfully overwritten (query parameter `overwrite` was set to `true`) * `412/Precondition-Failed` failure, not allowed to copy onto an exising resource * `MOVE` has the exact same parameters and return code & value as `COPY` #### Parameters ##### Path parameters http://127.0.0.1:{port}/{urlPrefix}/id/{id} * **`port`** TCP port * **`urlPrefix`** server path * **`id`** resource IDs. Even when readable, those resources need to be handled as if they were opaque values. ##### Query parameters * **`name`** File or folder name, for creation methods (`MKCOL`, `PUT`, `COPY`, `MOVE`). This is required, as the resource `id` is not (yet) known. * **`folderId`** target folder `id` used by `COPY` and `MOVE` methods. * **`overwrite`** when set to `true` with the `COPY`, `MOVE` and `PUT` methods, causes the target resource to be overwritten (not merged) in case it already exists. When absent, `overwrite` defaults to `false`. * **`depth`** is only valid with the `PROPFIND` method. It defines the recursion level of the request in the folder tree. When omitted, it defaults to `1` (list immediate child resources of a folder). The special value `infinity` causes the methods to recurse to the deepest possible level in the folder tree. ### Run Test Suite **New** the test suite does not cover the former verbs used by Hermes, and implemented into `filesystem/index.js`. So far, only hermes local filesystem access comes with a (small) test suite, that relies on [Mocha](http://visionmedia.github.com/mocha/) and [Should.js](https://github.com/visionmedia/should.js). Run it using: $ test/mocha/bin/mocha hermes/fsLocal.spec.js To stop on the first failing case: $ test/mocha/bin/mocha --bail hermes/fsLocal.spec.js For more detailled instructions, refer to the [Mocha home page](http://visionmedia.github.com/mocha/). ### Local Filesystem Service[](id:local-filesystem-service) The `fsLocal` service is simply serves your local machine's filesystem to the browser, which has otherwise no access outside the web sandbox (or exclusivelly via direct user interaction). Optionally, configure the `root` of your local file-system access in `ide.json`. By default, the local filesystem service serves the files from your _Home_ directory, depending on your operating system. You might want to change this to point to the location of your project files, to make navigation faster & easier. For instance, you can change `@HOME@` to `@HOME@/Documents` or to `D:\\Users\\Me` (if using backslashes [i.e. on Windows], use double slashes for JSON encoding) % vi ide.json [...] "command":"@NODE@", "params":[ "hermes/fsLocal.js", "-P", "/files", "-p", "0", "@HOME@" ], [...] ### Dropbox Filesystem Service[](id:dropbox-filesystem-service) Ares comes with an Hermes service using your Dropbox account as a storage service. Enable this service in the `ide.json` before starting the IDE server: [...] { "active":true, "id":"dropbox", "icon":"dropbox.com-32x32", "name":"Dropbox", "type": "filesystem", "provider": "hermes", "command":"@NODE@", "params":[ "hermes/fsDropbox.js", "-P", "/files", "-p", "10002" ], "auth": { "type": "dropbox", "appKey": "", "appSecret": "" } [...] } You need to replace the appKey and appSecret entries with the proper values from your Dropbox application entry for Ares(see below). The icon is not provided. In order to use Dropbox as storage service for Ares, you need to [create an Ares application in Dropbox](https://www.dropbox.com/developers/apps) & grant Ares the authorization to access this Dropbox application (_Ares_ > _Accounts_ > _Dropbox_ > _Renew_ ). Popup blockers must be disabled to allow the Dropbox OAuth popup window to appear. **NOTE:** While Chrome & Firefox will notify you of a blocked popup (hence allowing you to explicitly un-block it), Safari users will need to explicitly allow every popups (unless there is s smarter way am not aware of) using _Safari_ > _Preferences_ > _Security_ > Un-check _Block pop-up windows_ **NOTE:** Ares gives 20 seconds to the browser to load the Dropbox authorization window & complete the procedure. In case it takes longer, please press _Renew_ again: another immediate attempt will be faster as the page will be partially available from the browser cache. Ares Dropbox connector works behind an enterprise HTTP/HTTPS proxy, thanks to the [GitHub:node-tunnel](https://github.com/koichik/node-tunnel) library. `fsDropbox` proxy configuration embeds a `node-tunnel` configuration. For example, fellow-HP-ers can use the below (transform `Xproxy` into `proxy` in the sample ide.json): [...] "proxy":{ "http":{ "tunnel":"OverHttp", "host":"web-proxy.corp.hp.com", "port":8080 }, "https":{ "tunnel":"OverHttp", "host":"web-proxy.corp.hp.com", "port":8080 } }, [...] ## Project template services[](id:project-template-services) The service **genZip** allows to intanciate new Ares project from project templates such as [Enyo Bootplate](https://github.com/enyojs/enyo/wiki/Bootplate) or any customer specific project templates. These project templates can be defined in: * `ide.json` located in the `ares-project` installation directory * `ide-plugin.json` located in _each_ Ares plugin installation directory See [Project template configuration](#project-template-configuration) and [Merging Ares plugin configuration](../README.md#merging-configuration) for more information. ### Project template configuration[](id:project-template-configuration) The property `sources:` of the service **genZip** lists the template definitions that are available at project creation time. It is defined in the `ide.json` of ares-project. "sources": [ { "id": "bootplate-nightly", "type": "template", "description": "Enyo bootplate for webOS - Nightly", "files": [ { "url": "bootplate-latest.zip", "alternateUrl": "http://nightly.enyojs.com/latest/bootplate-latest.zip", "prefixToRemove": "bootplate", "excluded": [ "bootplate/api" ] } ] }, [...] ] Ares plugins can add or modify this list of templates, from their own `ide-plugin.json`. { "id": "genZip", "sources": [ { "id": "bootplate", "type": "null" }, { "id": "bootplate-nightly", "type": "template", "description": "Enyo bootplate for webOS - Nightly", "files": [ { "url": "bootplate-latest.zip", "alternateUrl": "http://nightly.enyojs.com/latest/bootplate-latest.zip", "prefixToRemove": "bootplate", "excluded": [ "bootplate/api" ] } ] }, ] } In the example above, `{ "id": "bootplate" }` will remove the entry defined in the main `ide.json` and `{ "id": "bootplate-nightly" ... } will add a new template. ### Protocol #### Resources The default `` value is `/genzip`. Its value can be changed using the `-P` paraemter in the main `ide.json` configuration file. * `/templates`: * `GET` returns a JSON-encoded array of all the available project templates. * `/template-repos/:repo-id`: * `POST` creates a new repo entry with the key `repo-id`. The POST body must contain the `url` of the new project template repository. * `/generate`: * `POST` returns a FormData containing all the files, encoded in base64, of the selected project template. * The POST body must contain: * the `templateId` of the selected project template. * the `substitutions` needed as a JSON stringified object. * It's up to the caller to extract and base64 decode the files to create a new project. In Ares, this is achieved by forwarding the FormData to Hermes filesystem service via a PUT method. ## Build services[](id:build-services) ### Ares IDE - Javascript API 1. `MyBuildService#buildPkg(project)` where `project` is an instance of `Ares.Model.Project` as found in the `ProjectView`. This kind has (among others) the following entry points: * `Ares.Model.Project#getName()`: Application Name * `Ares.Model.Project#getService()`: File-System service hosting the application project (source code) * `Ares.Model.Project#getFolderId()`: File-System service folderId of the application project (source code) root folder * `Ares.Model.Project#getConfig`: Application project configuration (from `project.json`) for that specific builder (from `build.`, as set by the service UI) ### Web Resources Although it can rely on other remote or local resources, Ares build services may share a maximum amount of source code with other build services by implementing the following resources using a shared semantic. The following resources * `/config`: * POST: pass the `ide.json` consolidated content for this specific service. This resource is only accessed from the Ares server: it is not proxied to the Ares IDE. * Query-Params: n/a * Request-Headers: n/a * Request-Body: * `application/json` the consolidated `ide.json` for this specific service * Response-Headers: n/a * Response-Body: n/a * `/user`: * GET: return user account information. Might be used to set a client-side cookie with proper authentication. This resource is generally called from the Ares _Accounts_ configuration wizard (the Ares IDE plugin that comes with a build service). * `/op/build` * POST: start a new build * Query-Params: n/a * Request-Headers: `Content-Type:` (`Authorization:` or `Cookies:` headers may also be present) * Request-Body: * `multipart/form-data` sequence of files that constitute the application source code. The relative file location is encoded the URL-way (with `/` directory separator) in each part `filename` field. The per-part `content-type` is always ignored & considered as `application/octet-stream` in order to not modifiy the original application source code before passing to the back-end build service. * Response-Headers: n/a * Response-Body: * `text/plain` build has failed (see HTTP response code) or is asynchronous * `multipart/form-data` generated application package is the first returned part of the multipart response ### Archive build service[](id:archive-build-service) This is the `arZip.js` service. It takes 2 arguments: * `pathname` * `port` It can be started standlone using the following command-line (or a similar one): ...in which case it can be tested using `curl` by a command-line like the following one: $ curl \ -F "file=@config.xml;filename=config.xml" \ -F "file=@icon.png;filename=images/icon.png" \ -F "archive=myapp.zip" \ "http://127.0.0.1:9019/arZip" > /tmp/toto.zip % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 8387 0 3860 100 4527 216k 253k --:--:-- --:--:-- --:--:-- 276k The generated file is expected to look like to below: $ unzip -l /tmp/toto.zip Archive: /tmp/toto.zip Length Date Time Name -------- ---- ---- ---- 942 10-17-12 17:26 config.xml 3126 10-17-12 17:26 images/icon.png -------- ------- 4068 2 files ### PhoneGap build service[](id:phonegap-build-service) Ares includes the ability to package a mobile Enyo application using [PhoneGap Build](https://build.phonegap.com/). You must have a properly setup account (with signing keys & distribution certificates) before being able to use Ares to build applications using PhoneGap Build. Here are a few references to create the necessary signing keys & distribution certificates: 1. [Android Application Signing](http://developer.android.com/tools/publishing/app-signing.html) #### Configuration The Ares PhoneGap build service does not need any configuration but the HTTP/HTTPS proxy, if needed. In `ide.json`, replace `XproxyUrl` by `proxyUrl` and a proxy protocol, host & port that match your needs. ``` "useJsonp":false, "verbose": false, "XproxyUrl": "http://web-proxy.corp.hp.com:8080", "auth": { [...] } ``` **NOTE:** Ares does not currently work behind a password-protected proxy. Should you need this feature, please report it via JIRA or on our user's forum. #### PhoneGap Build Plugins Ares does not have yet a UI to define which external plugins are to be included in the built application. However there is a workaround to integrate external plugins by editing the file `config.xml` associated with the project: Select _Project_ > _Edit_ > _PhoneGap Build_ > _Build Options_ and uncheck the box _Generate config.xml file when building. Here is an exemple of external plugin definition: ```xml ``` **References:** Here are the online PhoneGap Build documentation on [How to use plugins from your application](https://build.phonegap.com/docs/plugins-using) and [the list of available PhoneGap Build plugins & their respective description](https://build.phonegap.com/plugins). #### Implementation The entire [build.phonegap.com API](https://build.phonegap.com/docs/api) is wrapped by a dedicated Hermes build service named `bdPhoneGap` that use a [PhoneGap-provided Node.js client library](https://github.com/phonegap/phonegap-build-api-js#phonegap-build-api-js-). #### Protocol Resources: * The default `` value is `/phonegap`. Its value can be changed using the `-P` paraemter in the main `ide.json` configuration file. * `/token`: * `GET` using Basic Authentication, returns a JSON-encoded token object `{"token":"YOUR_TOKEN"}`. Every other resources are accessible only when passing this token value using on of the following ways: * As a `token` cookie with value `YOUR_TOKEN` (preferred), * As a web-form `token` field (either in `application/x-www-urlencoded` or `multipart/forma-data` format) if applicable to the request format. * As a `token=YOUR_TOKEN` query parameter, in the URL (_least secure, may be removed in the future_). * `/user`: * `GET`, returns the user account information, using the same format as the one returned by [`GET https://build.phonegap.com/api/v1/me`](https://build.phonegap.com/docs/read_api). * `/deploy`: * `POST` runs the Enyo `deploy.js` script on the given application. Application folder tree is encoded as a `multipart/form-data` in the POST request body. If successfull, the response body is a `application/zip` containing the deployable application. It is an intermediate step of the `/build` operation. * `/build`: * `POST` uploads the former deployable application to the [PhoneGap Build Service](https://build.phonegap.com) & returns the JSON-encoded answer of this service. This operation expects some fields (`key=value`) to be passed inlined in the request body (as `multipart/form-data` fields). Each of those field is passed verbatim as a property of the JSON requestObject (see [mantatory & optionnal parameters of the PhoneGap write API](https://build.phonegap.com/docs/write_api)). The following fields are mandatory. * `title` is the human-readable application name. It is considered a good practice to reuse the value of the `` field of the `config.xml`. #### Development & Test **Note:** Most of the commands in this section assume that you are using Mac OSX or Linux. Manual run on fixed port 10003 (default is dynamically-assigned port): $ node hermes/bdPhoneGap.js -p 10003 Test `/token`: * Assuming you have a working account build.phonegap.com associated with the email `YOUR_EMAIL`, get your PhoneGap developer token `YOUR_TOKEN`, using **build.phonegap.com**: $ curl -v -u YOUR_EMAIL -X POST -d "" https://build.phonegap.com/token Enter host password for user 'YOUR_EMAIL': {"token":"YOUR_TOKEN"} * Using **bdPhoneGap**: $ curl -v -X POST -d "username=YOUR_EMAIL" -d "password=YOUR_PASSWORD" http://127.0.0.1:10003/phonegap/token {"token":"YOUR_TOKEN"} Test `/api/v1/me`: * Using **build.phonegap.com**, use one of the below: $ curl -v -u YOUR_EMAIL -X GET -d "" https://build.phonegap.com/api/v1/me $ curl -v -X GET https://build.phonegap.com/api/v1/me?auth_token=YOUR_TOKEN * Using **bdPhoneGap**: $ curl -v -X GET -b "token=YOUR_TOKEN" http://127.0.0.1:10003/phonegap/api/v1/me Test `/op/deploy`: * The following commands generates a POST request carrying a `multipart/form-data` message suitable to test the `bdPhoneGap.js` service: * This one generates a command that returns a minified (deployable) application $ find . -type f | \ awk 'BEGIN{printf("curl ");}{sub("^\.\/", "", $1); printf("-F \"file=@%s;filename=%s\" ", $1, $1);}END{print(url)}' \ url=http://127.0.0.1:9029/phonegap/deploy/ Test `/op/build`: * This one generates a command that creates a new `appId` using an application located in the current directory. Note that you must provide the `token` and `title` form fields. The `` in the `config.xml` is a suitable value for the `title` form field. $ find . -type f | \ awk 'BEGIN{printf("curl ");}{sub("^\.\/", "", $1); printf("-F \"file=@%s;filename=%s\" ", $1, $1);}END{printf("-F \"token=%s\" -F \"title=%s\" %s\n", token, title, url)}' \ token=YOUR_TOKEN \ title="My First PhoneGap App" \ url=http://127.0.0.1:9029/phonegap/build/ * This one generates a command that updates the `appId=238006`. Other form fields follow the same rules as before. $ find . -type f | \ awk 'BEGIN{printf("curl ");}{sub("^\.\/", "", $1); printf("-F \"file=@%s;filename=%s\" ", $1, $1);}END{printf("-F \"token=%s\" -F \"title=%s\" -F \"appId=%s\" %s\n", token, title, appId, url)}' \ token=YOUR_TOKEN \ title="My First PhoneGap App" \ appId=YOUR_APPID \ url=http://127.0.0.1:9029/phonegap/build/ **Note:** In case you are working from behind the HP firewall (without ), you may need to prefix the `curl` and `node` commands above with `env https_proxy=web-proxy.corp.hp.com:8080`. ## Test services ### Javascript API - Ares IDE **TBC** * `MyTestService#runApp(project)` * `MyTestService#debugApp(project)` ### Web Resources **TBC** ## Debug It is possible to debug an Hermes services by commenting-out the `command` property of the service to be debugged in the ide.json & start it manually along with `--debug` or `--debug-brk` to later connect a `node-inspector`. Start the file server: $ node ares-project/hermes/filesystem/index.js 9010 hermes/filesystem/root **Debugging:** The following sequence (to be run in separated terminals) opens the ARES local file server in debug-mode using `node-inspector`. $ node --debug ares-project/hermes/filesystem/index.js 9010 hermes/filesystem/root ...then start `node-inspector` & the browser windows from a separated terminal: $ open -a Chromium http://localhost:9010/ide/ares/index.html $ node-inspector & $ open -a Chromium http://localhost:8080/debug?port=5858 ## Mapping more file-systems To map another file-system, you have to enable it in ide.json before starting the IDE server by changing "active" parameter and also by changing the value associated with the --root parameter: [...] { "active":false, "id":"Example", "icon":"$harmonia/images/providers/box_white-32x32.png", "name":"Example drive", "type": ["filesystem"], "provider": "hermes", "command":"@NODE@", "params":[ "@INSTALLDIR@/hermes/fsLocal.js", "--level", "http", "--pathname", "/files", "--port", "0", "--root", "@HOME@\\Example dir" ], "useJsonp":false, "verbose": false, "respawn": false } [...] Change name and id parameters. You can replace box_white-32x32.png by an appropriate app icon in the icon parameter. - Using Google Drive directory First install Google Drive App. You can donwload it from [here](here "https://tools.google.com/dlpage/drive"). Make a copy of the example above and perform specific changes for the Google Drive directory. [...] { "active":true, "id":"Google Drive", "icon":"$harmonia/images/providers/box_white-32x32.png", "name":"Google Drive Directory", "type": ["filesystem"], "provider": "hermes", "command":"@NODE@", "params":[ "@INSTALLDIR@/hermes/fsLocal.js", "--level", "http", "--pathname", "/files", "--port", "0", "--root", "@HOME@\\Google Drive" ], "useJsonp":false, "verbose": false, "respawn": false } [...] The icon is not provided. You can check the terms of use of the Google Drive branding [here](https://developers.google.com/drive/branding) and add an appropriate icon. Don't forget to check the --root parameter to your Google Drive directory in the following line: [...] "command":"@NODE@", "params":[ "@INSTALLDIR@/hermes/fsLocal.js", "--level", "http", "--pathname", "/files", "--port", "0", "--root", "@HOME@\\Google Drive" ] [...] For example, on MacOS, this line can be: [...] "command":"@NODE@", "params":[ "@INSTALLDIR@/hermes/fsLocal.js", "--level", "http", "--pathname", "/files", "--port", "0", "--root", "@HOME@/Google Drive" ] [...] - Using Box Sync directory First install Box Sync App. You can donwload it from [here]("https://www.box.com/pricing/"). Make a copie of example above and perform specific changes for the Box Sync directory. [...] { "active":true, "id":"Box", "icon":"$harmonia/images/providers/box_white-32x32.png", "name":"Box Sync Directory", "type": ["filesystem"], "provider": "hermes", "command":"@NODE@", "params":[ "@INSTALLDIR@/hermes/fsLocal.js", "--level", "http", "--pathname", "/files", "--port", "0", "--root", "@HOME@\\Documents\\My Box Files" ], "useJsonp":false, "verbose": false, "respawn": false } [...] The icon is not provided. You can add an appropriate icon from [here](https://www.google.com/?q=box.net+icon#q=box.net+icon). Don't forget to check the --root parameter to your Box Sync directory in the following line: [...] "command":"@NODE@", "params":[ "@INSTALLDIR@/hermes/fsLocal.js", "--level", "http", "--pathname", "/files", "--port", "0", "--root", "@HOME@\\Documents\\My Box Files" ] [...] For example, on MacOS, this line can be: [...] "command":"@NODE@", "params":[ "@INSTALLDIR@/hermes/fsLocal.js", "--level", "http", "--pathname", "/files", "--port", "0", "--root", "@HOME@/Box Documents" ] [...] ## References 1. [GitHub: node-inspector](https://github.com/dannycoates/node-inspector) 1. [Using node-inspector to debug node.js applications including on Windows (and using ryppi for modules)](http://codebetter.com/glennblock/2011/10/13/using-node-inspector-to-debug-node-js-applications-including-on-windows-and-using-ryppi-for-modules/) 1. Screencast [Debugging with `node-inspector`](http://howtonode.org/debugging-with-node-inspector) 1. [RFC4918 - HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)](http://tools.ietf.org/html/rfc4918) 1. [RFC5689 - Extended MKCOL for Web Distributed Authoring and Versioning (WebDAV)](http://tools.ietf.org/html/rfc5689)