Hi James,
I'd also like to figure out a better story for deploying assets on a CDN.
Here's a patch that makes your suggested change:
(We apply our patches as part of our deployment process.)
You can see it in action like so:
meteor create --example leaderboard
cd leaderboard
meteor bundle bundle.tgz
tar xf bundle.tgz
<download gist to root_url_path_prefix.patch>
patch -p0 < root_url_path_prefix.patch
<start local mongod instance in another terminal>
ROOT_URL_PATH_PREFIX=/bundle ROOT_URL=http://example.com/ PORT=3000 MONGO_URL=mongodb://localhost:27017/meteor node bundle/main.js
There are a few issues:
* Using an absolute url for ROOT_URL_PATH_PREFIX results in the following error being thrown:
/Users/alanning/src/js/meteor/leaderboard/bundle/programs/server/boot.js:185
}).run();
^
Error: a route URL prefix must begin with a slash
at _.extend.declare (packages/routepolicy/routepolicy.js:95)
at new StreamServer (packages/livedata/stream_server.js:23)
at new Server (packages/livedata/livedata_server.js:990)
at Package (packages/livedata/server_convenience.js:10)
at packages/livedata.js:3919:4
at packages/livedata.js:3930:3
at /Users/alanning/src/js/meteor/leaderboard/bundle/programs/server/boot.js:154:10
at Array.forEach (native)
at Function._.each._.forEach (/Users/alanning/src/js/meteor/leaderboard/bundle/programs/server/node_modules/underscore/underscore.js:79:11)
at /Users/alanning/src/js/meteor/leaderboard/bundle/programs/server/boot.js:81:5