Creates a manifest of the static files delivered to the client, for use by the app cache. The manifest is also designed to be usable to generate etag's for issue #626. In the original bundler code `self.css` and `self.js.client` starts out as an array of os-specific file paths and later becomes an array of URLs (including query parameters). While I tried to minimize code changes to avoid creating extra work for the engine project, this turned out to be too crazy to deal with. In this version `self.css` and `self.js.client` stay as file paths, and _generate_app_html now pulls the client URLs from the new manifest. This PR is thus proposing a design where the bundler manifest becomes the source of knowledge about client static resources included in the bundle, and is then used to generate the app html, the app cache, and perhaps etag's in the future. (If it made sense then the `load` list of server Javascript files could also be folded into the manifest, making the manifest the source of knowledge about all static resources... but the code in this PR don't include any steps in that direction).
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. If you do not run this script, Meteor will automatically download pre-compiled binaries when you first run it.
# OPTIONAL
./admin/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
Or install to /usr/local like the normal install process. This
will cause meteor to be in your PATH.
./install.sh
meteor --help
After installing, 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/
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
- Meteor help and discussion mailing list: https://groups.google.com/group/meteor-talk
- IRC:
#meteoronirc.freenode.net
Interested in contributing to Meteor?
- Core framework design mailing list: https://groups.google.com/group/meteor-core
- Contribution guidelines: https://github.com/meteor/meteor/wiki