The idea is that a distro maintainer wants to run something like the following command:
meteor publish-release clinical.meteor.rc6.json
Which will then allow users of the distro to run this:
meteor run --release clinical:[email protected]
A release manifest is similar to an NPM package.json file, in that it's primary concern is specify a list of Atmosphere packages, and providing a bit of metadata about that list of packages. The basic format looks like this:
{
"track":"distroname:METEOR",
"version&qu...
If you need to extend the meteor tool or the command line, you'll need to create and publish your own meteor-tool package. Ronen's documentation is the best out there for this process:
http://practicalmeteor.com/using-meteor-publish-release-to-extend-the-meteor-command-line-tool/1
It's easy to get...
StarryNight contains a small utility that parses an application's .meteor/versions file, and converts it into a Release Manifest.
npm install -g starrynight
cd myapp
starrynight generate-release-json
If you don't wish to use StarryNight, simply copy the contents of your .meteor/versions file i...
When building a custom release track, it's common to keep packages in the /packages directory as git submodules. The following command allows you to fetch all of the latest commits for the submodules in your /packages directory at the same time.
git submodule foreach git pull origin master
