Facebook is making a change on April 30th: all users of the previous unversioned Facebook API will automatically start using the 2.0 API, and the 1.0 API will be unavailable. By upgrading your Meteor to include this commit, you will be able to start adapting your app to the post-1.0 world now rather than next month. Full information about the changes to Facebook's APIs can be found at https://developers.facebook.com/docs/apps/upgrading If you only use Facebook integration for login via accounts-facebook, and don't use users' access tokens to access the Facebook API on their behalf, then the only changes you are likely to observe are: - The `id` returned by Facebook for users who had not previously used your app will be an "app-scoped ID". You cannot use these to directly correlate users between multiple apps (without using the Business Mapping API). This does not affect users who have already logged in to your app, so they will continue to be able to access your app. - Meteor asks for the `email` permission by default, and copies the `email` field from the `/me` object into the `serviceData.facebook` field on `Meteor.user()`, along with other fields which only require the `public_profile` permission. With 2.0, users can decline to grant all permissions other than `public_profile`, which means that you might not get their `email` address. You can use the `/me/permissions` API to tell if permissions were declined. Additionally, if you are accessing other Facebook APIs using the `access_token` returned via login, you should be aware that some permissions have changed in Facebook Graph API 2.0 and newer. Most notably, many operations involving friends need permissions such as `user_friends` to be explicitly requested now. Users can decline any permission (other than `public_profile`). Apps which need permissions other than `public_profile`, `email`, and `user_friends` may need to pass through a review stage before being fully activated. To change your app to request new permissions such as `user_friends`, specify the `requestPermissions` option to `Meteor.loginWithFacebook` (if you implemented your own login UI) or to `Accounts.ui.config` (if you are using the `accounts-ui` package). Note that while Meteor will now always use the v2.2 API to fetch the access token, it does appear that the access token can still be used to access pre-v2.2 APIs. For example, you can still use the access token to run FQL queries, even though FQL was removed in API v2.1. Fixes #3123.
Meteor
Meteor is an ultra-simple environment for building modern web applications.
With Meteor you write apps:
- in pure JavaScript
- that send data over the wire, rather than HTML
- using your choice of popular open-source libraries
Documentation is available at http://docs.meteor.com/
Quick Start
Install Meteor:
curl https://install.meteor.com | /bin/sh
Create a project:
meteor create try-meteor
Run it:
cd try-meteor
meteor
Deploy it to the world, for free:
meteor deploy try-meteor.meteor.com
Slow Start (for developers)
If you want to run on the bleeding edge, or help develop Meteor, you can run Meteor directly from a git checkout.
git clone git://github.com/meteor/meteor.git
cd meteor
If you're the sort of person who likes to build everything from scratch, you can build all the Meteor dependencies (node.js, npm, mongodb, etc) with the provided script. This requires git, a C and C++ compiler, autotools, and scons. If you do not run this script, Meteor will automatically download pre-compiled binaries when you first run it.
# OPTIONAL
./scripts/generate-dev-bundle.sh
Now you can run meteor directly from the checkout (if you did not build the dependency bundle above, this will take a few moments to download a pre-build version).
./meteor --help
From your checkout, you can read the docs locally. The /docs directory is a
meteor application, so simply change into the /docs directory and launch
the app:
cd docs/
../meteor
You'll then be able to read the docs locally in your browser at
http://localhost:3000/.
Note that if you run Meteor from a git checkout, you cannot pin apps to specific
Meteor releases or run using different Meteor releases using --release.
Uninstalling Meteor
Aside from a short launcher shell script, Meteor installs itself inside your home directory. To uninstall Meteor, run:
rm -rf ~/.meteor/
sudo rm /usr/local/bin/meteor
Developer Resources
Building an application with Meteor?
- Announcement list: sign up at http://www.meteor.com/
- Ask a question: http://stackoverflow.com/questions/tagged/meteor
- Discussion forums: https://forums.meteor.com/
Interested in contributing to Meteor?
- Issue tracker: https://github.com/meteor/meteor/issues
- Contribution guidelines: https://github.com/meteor/meteor/tree/devel/Contributing.md
We are hiring! Visit https://www.meteor.com/jobs to learn more about working full-time on the Meteor project.