https://github.com/gwendall/meteor-remote-ddp
Get your Meteor client point to any DDP server
https://github.com/gwendall/meteor-remote-ddp
Last synced: about 2 months ago
JSON representation
Get your Meteor client point to any DDP server
- Host: GitHub
- URL: https://github.com/gwendall/meteor-remote-ddp
- Owner: gwendall
- Created: 2015-03-19T16:43:36.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2017-08-07T14:16:14.000Z (almost 8 years ago)
- Last Synced: 2025-04-04T22:46:59.430Z (about 2 months ago)
- Language: JavaScript
- Size: 3.91 KB
- Stars: 10
- Watchers: 5
- Forks: 5
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
```diff
- NOTE: This package is not maintained anymore.
- If you want to help, please reach out to [email protected]
```
Meteor Remote DDP
=================
When building apps with decoupled client-code and server-code (say mobile apps, for example), your client tries to connect to its own DDP server by default. And performs all the Meteor methods (Meteor.call, Meteor.subscribe, etc.) to this endpoint.
This package just allows you to specify a remote DDP server for all of that.
Installation
------------
``` sh
meteor add gwendall:remote-ddp
```
How-to
----------
**RemoteDDP(url)**
``` javascript
RemoteDDP("http://localhost:5000");
// You can now call any Meteor method (call, subscribe, etc.) and it will all point to this server
```
Notes
-----
- Does not work in Cordova. To access a different server, use the --mobile-server flag instead.
- Inspired by @jamgold's [solution](https://github.com/meteor/meteor/issues/3852#issuecomment-78699162).
To do
-----
- Implement patch for OAUTH login (right now, accounts-facebook, accounts-twitter, etc point to client's server by default)
- Maybe monkey-patch Mongo.Collection so that it automatically picks the new Meteor.connection