SYNTAX
	mfpdev app push [<server <runtime>> [--password|-p <password>]]
	[--runtime-config | -r]

DESCRIPTION
	Sends, or pushes, a compressed file (.zip file format) containing one or 
	more configuration files that are associated with the application from your 
	local computer to a MobileFirst Server and updates the app's local client 
	properties file with the new server name and URL.
	
	You run the command from a directory or subdirectory of the app whose
	configuration you want to push.
	
	The configuration file that is pushed is the .zip file that was obtained by 
	previously running the 'mfpdev app pull' command. Native apps each have a 
	single .zip file. For Cordova apps, the separate .zip files that were 
	created for each platform are all pushed at one time.  Normally the .zip 
	files reside in the <app root>/mobilefirst directory, where they were 
	placed by the 'pull' command.
	
	The client properties file in which the server name and URL are replaced is 
	one of the following, depending on the app type:
	
	  Cordova - /config.xml
	  iOS native - /mfpclient.plist
	  Android native - /app/src/main/assets/mfpclient.properties
	  Windows native (Windows 10 UWP and Windows 8.1) - /strings/mfpclient.resw

	Note: If your Windows 8.1 native project contains both Windows 8.1 desktop
	and Windows Phone 8.1, two client properties files exist and are updated:

	  Windows Phone 8.1 - /WindowsPhone/strings/mfpclient.resw
	  Windows 8.1 desktop  - /Windows/strings/mfpclient.resw
	
	Optionally, you can choose to send a runtime configuration to the 
	server, if the runtime configuration exists on the local computer.
	

OPTIONS
	<server>:Name of an existing MobileFirst Server to push the configuration
	files to. The app must be currently registered to this server and the 
	server must be running.
	
	This parameter is optional. If you do not provide this parameter, the 
	default server is used. 
	
	You can set the default server when you define a server profile with 
	'mfpdev server add' or you can make an existing server the default when you
	run 'mfpdev server edit'. If you do not explicitly define a default server 
	and a MobileFirst server is detected that is running locally at
	http://localhost:9080, then this local server is used as the default, and it
	is given the name 'local'.
	
	<runtime>: Only valid when provided with a server name. Specifies
	the runtime on the server that the application will be pushed to. The 
	default runtime is 'mfp'.
	
	If this parameter is not specified and there are multiple runtimes on the 
	server, then you are prompted to choose a specific runtime. If the specified
	runtime does not exist on the server, you are prompted to choose an 
	existing runtime.

	[--password|-p <password>]: The password for the server's administrative 
	login ID.  The password specified here must match the password that is 
	defined on the MobileFirst Server. If you do not set this password in the
	local profile for the specified server, you must specify it with this 
	option or you will be prompted for it. 
	
	[--runtime-config | -r] Specifies that the runtime configuration should also
	be pushed to the server. By default the runtime configuration is not 
	pushed.

EXAMPLES

	$ mfpdev app push
	
	Pushes the application configuration for the app in the current directory to
	the default MobileFirst Server. The app's client properties file is modified
	to reflect the receiving server's profile name and URL.
	
	$ mfpdev app push ProdServer runtimeA -r
	
	Pushes the application configuration for the app in the current directory
	and the runtime configuration for runtimeA to a MobileFirst Server that has 
	profile name ProdServer. The app's client properties file is modified
	to reflect the ProdServer profile name and the server's URL.