meteor-sharejs

Meteor smart package for transparently adding ShareJS editors to an app. Includes CodeMirror and the Ace editor.

Demo app: http://documents.meteor.com (source)

Install

For vanilla ShareJS with text only:

$ meteor add mizzao:sharejs

For ShareJS with the Ace editor (note the explicit version, see #55):

$ meteor add mizzao:sharejs-ace@1.1.9

For ShareJS with the CodeMirror editor:

$ meteor add mizzao:sharejs-codemirror

Usage

No configuration necessary for anonymous document editing. If you want to integrate with Meteor accounts, see below.

Use this helper on the client to get a textarea with the specified docid (as an argument) and with a DOM id of "editor", for example:

{{> sharejsText docid=docid id="editor"}}

Use this helper to get an Ace editor. Make sure you specify a size (via CSS) on the #editor div or you won't see anything.

{{> sharejsAce docid=docid id="editor"}}

Use this helper to get a CodeMirror editor.

{{> sharejsCM docid=docid id="editor"}}

The templates will clean themselves up when re-rendered (i.e., you have several documents and docid changes.)

Client Configuration

For the Ace and CodeMirror editors, you can define onRender and onConnect callbacks in the options hash and use it to configure the editor. onRender is called when the editor is initially rendered, and onConnect is called after each successful connection to a document.

{{> sharejsAce docid=document onRender=config onConnect=setMode id="editor"}}

All standard Ace themes and extensions are supported. Note that the helper has to return a function inside of a function:

Template.foo.config = function () {
  return function(editor) {
    # Set some reasonable options on the editor
    editor.setTheme('ace/theme/monokai')
    editor.getSession().setMode('ace/mode/javascript')
    editor.setShowPrintMargin(false)
    editor.getSession().setUseWrapMode(true)
  }
};

Server Configuration

See this example config file for the various settings that you can use.

Persistence

By default, the documents and edit operations will be persisted in Meteor's Mongo database. Mongo is the recommended usage as you don't need a separate database and user integration is supported. "opsCollectionPerDoc": false can be useful to set if you don't want a separate ops collection for each document.

You can also use db.type of none to have all documents and operations in memory.

Meteor User-Accounts Integration

In case you are using Mongo to mirror the internal sharejs DB with an external Meteor collection as in the user-accounts demo app (find it here deployed on meteor), both authorization and authentication are available using the ShareJS auth mechanism.

The use of this feature becomes effective if you store addional metadata such as owners and invites in the document collection like here in the demo app.

Your settings file should look like the following:

1{
2  "sharejs": {
3    "options": {
4      "accounts_auth": {
5        "authorize": {
6            "collection": "documents",
7            "token_validations": {
8              "or": {
9                "invitedUsers": "is_in_array",
10                "userId": "is_equal"
11              }
12            },
13            "apply_on": [
14              "read",
15              "update",
16              "create",
17              "delete"
18            ]
19        },
20        "authenticate": {
21            "collection": "users",
22            "token_validations": {
23              "_id": "is_equal"
24            }
25        }
26      }
27    }
28  }
29}

All authorize and authenticate settings are under their respective categories. Please note that both of them are completely optional, however once present, they must have at least a field called collection.

sharejs.options.accounts_auth.authorize
sharejs.options.accounts_auth.authenticate

The sub-categories for both define the allowed operations and validation.

collection: database collection to fetch the document/user metadata from.
token_validations: contains the boolean logic and supports the keywords is_equal, isnt_equal, is_in_array and isnt_in_array. Both or and and logical operators can be used, provided at any one level of JSON, there is only one or none of them.
apply_on: you can select operations from here Type column except connect which is reserved for authentication.

Validations

All validations are run against the token. The client-side of sharejs auth would use Meteor.userId() for the token. So, for a returned document from database, the following will check for equality of userId and token or presence of token in invitedUsers.

1"token_validations": {
2  "or": {
3    "userId": "is_equal",
4    "invitedUsers": "is_in_array"
5  }
6}

Authentication

Usually, the presence of the user in the collection is sufficient for allowing the connection to sharejs. However, criteria such as the following can also be used.

1"token_validations": {
2  "_id": "is_equal"
3}

Advanced

You can access the ShareJS Server API at ShareJS.model. For example, you may want to delete documents ops when the document is deleted in your app. See the demo for an example.

Notes

When using the default mongo driver, you must not use collections called docs or ops. These are used by ShareJS.
When not using accounts integration, ShareJS is agnostic to the Meteor users, and doesn't keep track of who did what op. The document ids are used for access.
It's best to create a Meteor.Collection for your documents which generates good unique ids to connect to ShareJS with. Use these to render the templates above. See the demo for examples.
Importing ace dependencies is somewhat unsatisfactory. Waiting for improvements to Meteor package management system.

Please submit pull requests for better features and cooperation!

Contributors

Andrew Mao (https://github.com/mizzao/)
Karan Batra-Daitch (https://github.com/kbdaitch)
CJ Carr (https://github.com/cortexelus)
David Sichau (https://github.com/DavidSichau)