We want to support running DDP through a corporate proxy, but the
higher-level faye-websocket can't support that and won't be changed to
allow that: https://github.com/faye/faye-websocket-node/pull/30
Fair enough. Let's just switch to the lower-level module, since we don't
care about getting a browser-compatible websocket API.
This is a first step towards fixing #2515.
This way the size check takes calls to Meteor.AppCache.config()
into account, so users can remove files from the cache and get
rid of the warning.
Also, add an internal option to totally disable the warning and
use it in tests.
* Add a test to verify section header unicity
* Add a test to verify NETWORK section content
* Simplify the regular expressions used in the manifest content test.
Clean up on every soft restart (every time the js app loads) not on every hard
restart (every time the native shell loads). This fixes the problem described
in issue #2727: HCP cache keeps accumulating in development mode leading to
crashes.
The server sends hot code push updates to mobile clients with ROOT_URL
and DDP_DEFAULT_CONNECTION_URL taken from the MOBILE_ROOT_URL and
MOBILE_DDP_URL environment variables. These are set by the main meteor
process when it starts the app runner.
* --port now requires a port ('meteor run --port example.com' isn't valid).
* --mobile-server defaults to your detected IP address and the port from
--port.
* If you provide a value for --mobile-server, we default to http:// as
the protocol. A host is required for --mobile-server if you don't omit
the option entirely. Similar for the --server argument to 'meteor
build'.
This commit includes the 'netroute' npm module as a core package (which
has binary dependencies) for IP detection. It would be nice to put it in
packages/non-core, but I think it has to be a core package in order to
uniload it.
