Ext.data.JsonP.command_reference({"title":"Sencha Cmd Reference","guide":"
Contents
\nInvokes the embedded version of Apache Ant providing the cmd.dir
property to\naccess Sencha Cmd using the following taskdef
:
<taskdef resource=\"com/sencha/ant/antlib.xml\"\n classpath=\"${cmd.dir}/sencha.jar\"/>\n
\n\nThis command recognizes the -Dproperty=value
syntax for properties used by\nAnt, even though this does not conform to normal Sencha Cmd parameter syntax.\nSimilar to directly invoking Ant, this command defaults to \"build.xml\"
for\nthe script file basing its search on the current directory or the value of the\n-cwd
switch passed to sencha
.
For example, the following command uses \"../build.xml\"
as the script and\npasses in the foo
property as \"42\" when executing the default target (since\nno target was specified).
sencha -cwd=.. ant -Dfoo=42\n
\n\n--debug
, -d
- Enables Ant debug level messages--file
, -f
- The Ant file to execute (default is build.xml)--props
, -p
- One or more properties for the Ant script (name=value,...)--target
, -t
- The target(s) to execute from the Ant script (comma separated)--verbose
, -v
- Enables Ant verbose level messagessencha ant [options] targets...\n
\n\ntargets
- The Ant script targets to executeThis category contains various commands for application management.
\n\npackage
- Packages a Sencha Touch application for native app storesbuild
- Executes the build process for an applicationrefresh
- Updates the application metadata (aka \"bootstrap\") fileresolve
- Generate dependencies in the loading order for the given app.upgrade
- Upgrade the current application to the specified SDKThis command builds the current application.
\n\nsencha app build [production|testing|native|package]\n
\n\nThis will build your application in its current configuration and generate the\nbuild output in the \"build/<environment>\"
folder. This location and many\nother properties can be configured in your application's configuration file\n\".sencha/app/sencha.cfg\"
or the provided build script \"build.xml\"
.
For locally overriding build properties, the build script loads an optional\nproperties file called \"local.properties\"
if present in your app folder. The\npurpose of this file is to define build properties that are in some way special\nto the local environment (that is, the local machine). As such, this file is\nnot intended to be tracked in source control.
This command is equivalent to running the provided Ant script directly using\nthe following command:
\n\nsencha ant [production|testing|native|package] build\n
\n\nTo tune the process, start by looking at the generated \"build.xml\"
in your\napp folder. The actual build logic is located in \".sencha/app/build-impl.xml\"
.
The \"build.xml\"
script can be used by many Continuous Integration (CI) systems\nif they understand Apache Ant (most do). If not, the Sencha Cmd command line\ncan be used as you would during development. If the CI system understands Ant,\nhowever, it is often more convenient to use that integration rather than using\na command line invocation.
--archive
, -a
- The directory path where all previous builds were stored.--clean
, -c
- Remove previous build output prior to executing build--destination
, -d
- The directory to which the build output is written--environment
, -e
- The build environment, either 'testing', 'production', 'package' (Touch Specific), or 'native' (Touch Specific).--run
, -r
- Enables automatically running builds with the native packagersencha app build [options] [environment] \\\n [destination] \\\n [archive]\n
\n\nThis category contains various commands for packing application for deployment\non phones using the Sencha Mobile Packager.
\n\nbuild
- Packages an app with the given configuration filegenerate
- Generates a Packager configuration JSON filerun
- Packages and tries to run the application for the given configuration JSON fileThis command creates a native package of the current application.
\n\n--path
, -p
- the path to the configuration filesencha app package build [options] path\n
\n\nThis command generates a Packager configuration JSON file.
\n\n--path
, -p
- the path to the configuration filesencha app package generate [options] path\n
\n\nThis command packages and runs the current application.
\n\n--path
, -p
- the path to the configuration filesencha app package run [options] path\n
\n\nThis command regenerates the metadata file containing \"bootstrap\" data for the\ndynamic loader and class system.
\n\nThis must be done any time a class is added, renamed or removed.
\n\nThis command can also update any required packages if you have added package\nrequirements to your application. To refresh required packages (which may\ndownload those packages from remote repositories), do this:
\n\nsencha app refresh --packages\n
\n\nThe additional parameters are seldom used.
\n\n--base-path
, -b
- The base path to use to calculate relative path information. Defaults to index.html directory--metadata-file
, -m
- The output filename for the js file containing the manifest metadata--packages
, -pac
- Update required packages from remote repositoriessencha app refresh [options] [metadata-file] \\\n [base-path]\n
\n\nGenerate a list of dependencies in the exact loading order for the current\napplication.
\n\nNOTE: the resolved paths are relative to the current application's HTML file.
\n\n--output-file
, -o
- The file path to write the results to in JSON format.--uri
, -u
- The URI to the application\\'s HTML documentsencha app resolve [options] uri \\\n output-file\n
\n\nThis command upgrades the current application (based on current directory) to a\nspecified new framework.
\n\nsencha app upgrade /path/to/sdk\n
\n\nNOTE: This will upgrade the framework used by the current application in the\ncurrent workspace. This will effect any other applications in this workspace\nusing the same framework (i.e., \"ext\" or \"touch\").
\n\nTo upgrade just the generate scaffolding of your application to a new version\nof Sencha Cmd and not the framework in use, do this:
\n\nsencha app upgrade --noframework\n
\n\n--noappjs
, -noa
- Disable upgrade of app.js--noframework
, -nof
- Upgrade only the Sencha Cmd scaffolding and not the SDK--path
, -p
- The path to the framework to which to upgradesencha app upgrade [options] [path]\n
\n\nThis command is used to process a legacy JSBuilder (\"jsb\") file.
\n\nDEPRECATED: This command is provided for backwards compatibility with previous\nreleases. It is highly recommended to migrate applications to the new compile
\ncommand and discontinue use of this command.
sencha build \n
\n\n--native
, -n
- Enables / disables calls to system installed MRI compass--ruby-path
, -r
- set the path to MRI ruby executableThis command category provides JavaScript compilation commands. The compile
\ncategory maintains compilation state across its sub-commands so using and
to\nconnect sub-commands can provide significant time savings compared to making\nrepeated calls.
--classpath
, -cl
- Add one or more folders to the classpath--debug
, -d
- Enable the debug option for the js directive parser--ignore
, -ig
- Ignore files in the classpath with names containing substrings (comma separated)--options
, -o
- Sets options for the js directive parser (name:value,...)--prefix
, -p
- The file with header or license prefix to remove from source filesconcatenate
- Produce output file by concatenating the files in the current setexclude
- Exclude files from the current set matching given criteriainclude
- Add files to the current set matching given criteriaintersect
- Intersect specified saved sets to produce a new setmetadata
- Generates information about the classes and files in the classpathpage
- Compiles the content of a page of markup (html, jsp, php, etc)pop
- Pops the current set back to the most recently pushed set from the stackpush
- Pushes the current set on to a stack for later pop to restore the current setrestore
- Restores the enabled set of files from a previously saved setsave
- Stores the currently enabled set of files by a given nameshow-ignored
- Shows any files being ignored in the classpathunion
- Similar to include but selects only the files that match the given criteriaThis command writes the current set to the specified output file.
\n\n--append
, -a
- Appends output to output file instead of overwriting output file--beautify
, -b
- enables / disables beautification of sources after compilation--closure
, -cl
- Compress generate file using Closure Compiler--compress
, -co
- Compress generated file using default compressor (YUI)--output-file
, -o
- The output file name (or $ for stdout)--remove-text-references
, -r
- enables / disables reference optimization by converting string classnames to static references--strip-comments
, -st
- Strip comments from the generated file--uglify
, -u
- Compress generate file using uglify-js--yui
, -y
- Compress generated file using YUI Compressorsencha compile concatenate [options] output-file\n
\n\nThis command removes from the current set any files matching the criteria.
\n\n--all
, -a
- Select all files in global cache (ignores other options)--class
, -c
- Selects files according to the specified class names--file
, -f
- Selects the specified file names (supports glob patterns)--namespace
, -na
- Selects all files with class definitions in the given namespace(s)--not
, -no
- Inverts the matching criteria--recursive
, -r
- Enable traversal of dependency relationships when selecting files--set
, -s
- Selects files from on a previously saved set (ignores other options)--tag
, -t
- Selects all files with the specified '//@tag' valuessencha compile exclude [options] \n
\n\nThis command adds the files matching the criteria to the current set.
\n\n--all
, -a
- Select all files in global cache (ignores other options)--class
, -c
- Selects files according to the specified class names--file
, -f
- Selects the specified file names (supports glob patterns)--namespace
, -na
- Selects all files with class definitions in the given namespace(s)--not
, -no
- Inverts the matching criteria--recursive
, -r
- Enable traversal of dependency relationships when selecting files--set
, -s
- Selects files from on a previously saved set (ignores other options)--tag
, -t
- Selects all files with the specified '//@tag' valuessencha compile include [options] \n
\n\nThis command produces as in the current set the files that are contained in all\nof the specified input sets. Alternatively, this command can include files that\nare present in a present in a certain minimum number of sets.
\n\nThis command only operates on saved sets (unlike most other set operations).
\n\n--min-match
, -m
- The minimum number of sets containing a file to cause a match (-1 = all)--name
, -n
- The name by which to save the intersection as a set--sets
, -s
- The sets to include in the intersectionsencha compile intersect [options] \n
\n\nThis command generates various forms of metadata extracted from the current set\nof files. This data can be exported in various formats (e.g., JSON or JSONP).
\n\nChoose one of the following options
\n\n--alias
, -ali
- Generate class name to alias information--alternates
, -alt
- Generate class alternate name information--definitions
, -d
- Generate symbol information--filenames
, -f
- Generate source file name information--loader-paths
, -l
- Generate dynamic loader path information--manifest
, -m
- Generate a class definition manifest fileChoose one of the following options
\n\n--json
, -json
- Generate data in JSON format--jsonp
, -jsonp
- Generate data in JSONP format using the given function--tpl
, -t
- The line template for generating filenames as text (e.g. )--append
, -ap
- Appends output to output file instead of overwriting output file--base-path
, -b
- Set the base path for relative path references--output-file
, -o
- The output file name (or $ for stdout)--separator
, -s
- The delimiter character used to separate multiple templatessencha compile metadata [options] \n
\n\nThis command processes a markup file as input and generates an output file with\ncertain sections rewritten.
\n\nIf the -name
option is specified, the dependency graph of all required files\nis saved as a file set with that name (see also the save
command).
If the -name
option is not specified, all required files are instead written\nto the \"all-classes.js\" file.
--append
, -ap
- Appends output to output file instead of overwriting output file--beautify
, -b
- enables / disables beautification of sources after compilation--classes-file
, -cla
- the name of the js file containing the concatenated output--closure
, -clo
- Compress generate file using Closure Compiler--compress
, -co
- Compress generated file using default compressor (YUI)--input-file
, -i
- the html page to process--name
, -n
- sets a reference name for the page--output-page
, -o
- the output html page--remove-text-references
, -r
- enables / disables reference optimization by converting string classnames to static references--scripts
, -sc
- inject the given script path into the generated markup ahead of the all classes file--strip-comments
, -str
- Strip comments from the generated file--uglify
, -u
- Compress generate file using uglify-js--yui
, -y
- Compress generated file using YUI Compressorsencha compile page [options] output-page\n
\n\nThis command restores the current set of files from the \"stack\". This state was\npreviously put on the \"stack\" using the push
command.
sencha compile ... \\\n and push \\\n and ... \\\n and pop\n and ...\n
\n\nBetween the push
and pop
commands the current file set can be adjusted as\nneeded and then restored for subsequent commands.
sencha compile pop \n
\n\nThis command saves the current set of files on a \"stack\" to easily save and\nrestore state.
\n\nsencha compile ... \\\n and push \\\n and ... \\\n and pop\n and ...\n
\n\nBetween the push
and pop
commands the current file set can be adjusted as\nneeded and then restored for subsequent commands.
sencha compile push \n
\n\nsencha compile restore String\n
\n\nsencha compile save String\n
\n\nDisplays a list of all files found in the classpath
but matching an -ignore
\ncriteria.
sencha compile show-ignored \n
\n\nThis command adds files matching the criteria to the current set. This is\nsimilar to the include
command except that this command first removes all\nfiles from the current set. In other words, this command makes the current set\nequal to only those files that match the criteria.
--all
, -a
- Select all files in global cache (ignores other options)--class
, -c
- Selects files according to the specified class names--file
, -f
- Selects the specified file names (supports glob patterns)--namespace
, -na
- Selects all files with class definitions in the given namespace(s)--not
, -no
- Inverts the matching criteria--recursive
, -r
- Enable traversal of dependency relationships when selecting files--set
, -s
- Selects files from on a previously saved set (ignores other options)--tag
, -t
- Selects all files with the specified '//@tag' valuessencha compile union [options] \n
\n\nThis command can be used to either set configuration options singly or load a\nconfiguration file to set multiple options.
\n\nBecause these configuration options are only held for the current execution of\nSencha Cmd, you will almost always use then
to chain commands that will now\nbe executed with the modified configuration.
For example, to change the theme of an Ext JS application for a build:
\n\nsencha config -prop app.theme=ext-theme-neptune then app build\n
\n\nMultiple properties can be loaded from a properties file:
\n\nsencha config -file neptune.properties then app build\n
\n\nThe content of \"neptune.properties\"
might be something like this:
app.theme=ext-theme-neptune\napp.build.dir=${app.dir}/build/neptune\n
\n\nIn this case, an alternative would be to set app.dir
in the applications's\n\"sencha.cfg\"
file like so:
app.build.dir=${app.dir}/build/${app.theme}\n
\n\n--file
, -f
- The properties file to load--prop
, -p
- One or more property names and values to setsencha config [options] \n
\n\nThis category provides commands for manipulating files.
\n\nmirror
- Commands for making mirror images for RTL languagesweb
- Manages a simple HTTP file serverconcatenate
- Concatenate multiple files into onedifference
- Generates deltas between two files in JSON formatminify
- Minify a JavaScript fileslice
- Generates image slices from a given image directed by a JSON manifestThis command combines multiple input files into a single output file.
\n\nsencha fs concat -to=output.js input1.js input2.js input3.js\n
\n\n--from
, -f
- List of files to concatenate, comma-separated--to
, -t
- The destination file to write concatenated contentsencha fs concatenate [options] files...\n
\n\nThis command produces a delta (or \"patch\") file between input files.
\n\nsencha fs diff -from=base.js -to=modified.js -delta=patch\n
\n\nsencha fs difference \n
\n\nThis command produced minified files using various back-end compressors.
\n\nsencha fs minify -yui -from=in.js -to=out.js\n\nsencha fs minify -closure -from=in.js -to=out.js\n
\n\nThe legacy syntax is also supported:
\n\nsencha fs minify -compressor=yuicompressor -from=in.js -to=out.js\n\nsencha fs minify -compressor=closurecompiler -from=in.js -to=out.js\n
\n\n--closure
, -cl
- Enable the Google Closure Compiler--from
, -f
- The input js file to minify--to
, -t
- The destination filename for minified output.--yui
, -y
- Enable the YUI Compressorsencha fs minify [options] \n
\n\nCommands for create horizontal mirror of images and sprites for RTL locales.
\n\nThis family of commands is intended for automated production of \"derivative\"\nimages based on hand maintained and designed image assets authored in the more\nfamiliar, left-to-right (LTR) form.
\n\nall
- Horizontally flip a folder of images and sprites based on naming conventionimage
- Horizontally flip an imagesprite
- Horizontally flip a \"sprite\" (multi-cell image)This command creates horizontal mirror images of a folder of images and/or\nsprites. This command requires some name consistency in order to differentiate\noutput files from input files and the geometry of sprites.
\n\nSprites must have a name segment that looks like \"4x3\" to define its geometry.\nThis is understood as \"columns\" x \"rows\" or, in this example, 4 columns and 3\nrows.
\n\nThe following examples all fit this pattern:
\n\nThe input files and output files are separated by a suffix that must be given.\nTHe output files will be produced from the input files applying the suffix. By\ndefault, the output files are written to the same folder as the input files.\nThis can be changed by specifying \"-out\".
\n\nFor example:
\n\nsencha fs mirror all -r -suffix=-rtl /path/to/images\n
\n\nThe above command performs the following:
\n\n\"/path/to/images\"
(and all sub folders due to -r
) for images.\"-rtl\"
is considered an input file.-overwrite
.\"/path/to/images\"
.By passing the -format
switch, the format of the output images can be set\nto be other than the same format as the original file. For example, one could\nconvert PNG files to GIF by passing -format=gif
. This does only basic image\nconversion and no advanced image processing. Simple color quantization can be\nenabled using -quantize
.
For example:
\n\nsencha fs mirror all all -format=gif -ext=png -quantize -out=/out/dir \\\n -suffix=-rtl /some/pngs\n
\n\nThe above command will process all \"png\"
images and will write out their\n\"gif\"
versions (using color quantization) to a different folder.
--dry-run
, -d
- When set no images will be saved but all normal work is still done--extensions
, -e
- Comma-separated list of image extensions (default is \"gif,png\")--format
, -f
- The image format to write all output files (e.g., \"-f=png\")--output-dir
, -ou
- The output folder for generated images (defaults to input folder)--overwrite
, -ov
- Disable up-to-date check and always generate output file--quantize
, -q
- Enable basic color quantization (useful with -format=gif)--recurse
, -r
- Process the input folder recursively (i.e., include sub-folders)--suffix
, -s
- The suffix of output files (e.g., \"-rtl\")sencha fs mirror all [options] File\n
\n\nFile
- The input folder to processThis command create a horizontal mirror image of a given input file.
\n\nFor example
\n\nsencha fs mirror image foo.png foo-rtl.png\n
\n\nThe above command creates \"foo-rtl.png\"
from \"foo.png\"
.
sencha fs mirror image File \\\n File\n
\n\nThis command create a horizontal mirror image of the cells in a given sprite.
\n\nFor example
\n\nsencha fs mirror sprite -rows=2 -cols=4 sprite.png sprite-rtl.png\n
\n\nThe above command horizontally flips each cell in the 2x4 sprite \"sprite.png\"
\nand produces \"sprite-rtl.png\"
.
NOTE
: The number of rows and columns are required.
--columns
, -c
- The number of columns in the sprite.--rows
, -r
- The number of rows in the sprite.sencha fs mirror sprite [options] File \\\n File\n
\n\nThis command performs image slicing and manipulation driven by the contents of\na JSON manifest file. The manifest file contains an array of image area\ndefinitions that further contain a set of \"slices\" to make.
\n\nThis file and the corresponding image are typically produced for a Theme as\npart of the theme package build. For details on this process, consult this\nguide:
\n\nhttp://docs.sencha.com/ext-js/4-2/#!/guide/command_slice
\n\n--format
, -f
- The image format to save - either \"png\" or \"gif\" (the default)--image
, -i
- The image to slice--manifest
, -m
- The slicer manifest (JSON) file--out-dir
, -o
- The root folder to which sliced images are written--quantized
, -q
- Enables image quantization (default is true)--tolerate-conflicts
, -t
- Tolerate conflicts in slice manifestsencha fs slice [options] \n
\n\nThis category provides commands to manage a simple HTTP file server.
\n\n--port
, -p
- Set the port for the web serverstart
- Starts a static file Web Server on a portstop
- Stops the local web server on the specific portThis command starts the Web server and routes requests to the specified files.\nFor example:
\n\nsencha fs web -port 8000 start -map foo=/path/to/foo,bar=/another/path\n
\n\nGiven the above, the following URL entered in a browser will display the files\nin \"/path/to/foo\"
:
http://localhost:8000/foo\n
\n\nAnd this URL will display the files in \"/another/path\"
:
http://localhost:8000/bar\n
\n\nTo stop the server, press CTRL+C or run the sencha fs web stop
command:
sencha fs web -port 8000 stop\n
\n\n--mappings
, -m
- List of local folders (ex: [sub=]/path/to/folder)sencha fs web start [options] \n
\n\nThis command stops the Web server previously started by sencha fs web start
.
For example:
\n\nsencha fs web -port 8000 start -map foo=/path/to/foo,bar=/another/path\n
\n\nFrom another terminal or console, this will stop the server:
\n\nsencha fs web -port 8000 stop\n
\n\nsencha fs web stop \n
\n\nThis category contains code generators used to generate applications as well\nas add new classes to the application.
\n\napp
- Generates a starter applicationcontroller
- Generates a Controller for the current applicationform
- Generates a Form for the current application (Sencha Touch Specific)model
- Generates a Model for the current applicationpackage
- Generates a starter packageprofile
- Generates a Profile for the current application (Sencha Touch Specific)theme
- Generates a theme page for slice operations (Ext JS Specific)view
- Generates a View for the current application (Ext JS Specific)workspace
- Initializes a multi-app workspaceThis command generates an empty application given a name and target folder.
\n\nThe application can be extended using other sencha generate
commands (e.g.,\nsencha generate model
).
Other application actions are provided in the sencha app
category (e.g.,\nsencha app build
).
--controller-name
, -c
- The name of the default Controller--library
, -l
- the pre-built library to use (core or all). Default: core--name
, -n
- The name of the application to generate--path
, -p
- The path for the generated application--starter
, -s
- Overrides the default Starter App template directory--theme-name
, -t
- The name of the defualt Theme--view-name
, -v
- The name of the defalut Viewsencha generate app [options] name \\\n path\n
\n\nThis command generates a new Controller and adds it to the current application.
\n\n--name
, -n
- The name of the Controller to generatesencha generate controller [options] name\n
\n\nThis command generates a new form and adds it to the current application.
\n\n--fields
, -f
- Comma separated list of \"name:type\" field pairs--name
, -n
- The name of the Form to generate--xtype
, -x
- The xtype for the form. Defaults to the lowercase form of the name.sencha generate form [options] name \\\n fields \\\n [xtype]\n
\n\nThis command generates a new Model class and adds it to the current application.
\n\n--base
, -b
- The base class of the Model (default: Ext.data.Model)--fields
, -f
- Comma separated list of \"name:type\" field pairs--name
, -n
- The name of the Modelsencha generate model [options] name \\\n fields\n
\n\nThis command generates a new Sencha Cmd Package. A package is in many ways like\nan application in that it contains any of the following pieces:
\n\nAll of these are integrated by a build process using sencha package build
.
For example:
\n\nsencha generate package foo\n
\n\nTo use this package in applications (or other packages), you just add the name\nof the package to the requires array in the \"app.json\"
or \"package.json\"
\nfile:
requires: [\n 'foo'\n]\n
\n\nAll packages reside in the \"./packages\"
folder of the workspace (which is\noften the same folder as your application).
--name
, -n
- The name of the package to generate--type
, -t
- The type of the package to generate (i.e., \"code\" or \"theme\")sencha generate package [options] name\n
\n\nThis command generates a new Profile and adds it to the current application.
\n\nNOTE: Sencha Touch only.
\n\n--name
, -n
- The name of the Profile to generatesencha generate profile [options] name\n
\n\nThis command generates a new Theme. For Ext JS 4.1, themes are \"owned\" by an\napplication. In Ext JS 4.2 and beyond, themes are Packages.
\n\nIn Ext JS 4.2, theme packages can extend other themes. By default, generated\nthemes extend \"ext-theme-classic\". This can be overridden using --extend
.
To generate a stand-alone Theme in Ext JS 4.2, follow these steps. Generate a\nworkspace (with \"ext\"
folder) using Ext JS 4.2 SDK unzipped on your system:
sencha -sdk /path/to/ext-4.2.0 generate workspace MyWorkspace\ncd MyWorkspace\n
\n\nFrom inside the workspace, use the \"ext\"
folder to generate the theme package:
sencha -sdk ext generate theme --extend ext-theme-neptune MyTheme\n
\n\nThe above could equivalently have used the SDK used to create the workspace.
\n\nThe -sdk
switch is used here to indicate the framework on which the theme is\nbased. This is not needed if the command is run from an Ext JS application\nfolder.
NOTE:
Does not apply to Sencha Touch.
--extend
, -e
- The name of the theme package to extend (Ext JS 4.2+ only)--name
, -n
- The name of the Theme to generatesencha generate theme [options] name\n
\n\nThis command generates a new View class and adds it to the current application.
\n\n--name
, -n
- The name of the View to generatesencha generate view [options] name\n
\n\nThis command generates a workspace for managing shared code across pages or\napplications.
\n\n--path
, -p
- Sets the target path for the workspacesencha generate workspace [options] [path]\n
\n\nThis command displays help for other commands.
\n\nsencha help generate app\n
\n\nsencha help command...\n
\n\ncommand
- The command path for which to display help (e.g., \"generate app\"These commands give you access to all the tools required to create, manage and\ndeploy web applications in the io cloud.
\n\nSencha.io provides a backend-as-a-service that enables developers with a set of\nAPIs that helps them build and run their applications. It allows you to build\nweb applications using services provided through our client side SDKs, Ext JS\nand Sencha Touch.
\n\napp-set-group
- Sets the Auth Group associated with an appcreate-app
- Creates an app in Sencha.iocreate-auth-group
- Creates an auth group in Sencha.iocreate-version
- Creates a version of an app in Sencha.iodeploy
- Deploys a version of an application in Sencha.iolist-apps
- Lists all the apps for this developer in Sencha.iolist-groups
- Lists Authentication Groups for a Developerlist-versions
- Lists all the versions for this app in Sencha.ioset-group-auth
- Sets an Auth Group's authentication mechanismundeploy
- Undeploys a version of an application in Sencha.ioSets the Authentication Group which is associated with this Application.
\n\nOnly one Authentication Group may be associated with an Application at any\ngiven time.
\n\nAn Authentication Group controls which methods of authentication are available\nto users of your application. Users are members of Authentication Groups.
\n\n--group-name
, -g
- The Auth Group name to associate with this appsencha io app-set-group [options] [appName] \\\n [groupName] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nCreates a new Application in the context of Sencha Io.
\n\nsencha io create-app [appName] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nCreates a new Authentication Group in Sencha Io.
\n\n--group-name
, -g
- The Auth Group name to associate with this appsencha io create-auth-group [options] [groupName] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nCreates a new Version of an Application. In doing so, an application \".zip\"
\nfile is uploaded to the cloud, along with a version tag and a description of\nthis version. Once a version has been successfully created, it must be\ndeployed before it can be accessed.
--package-path
, -pac
- The path to the package to be used in a new application version.--version-description
, -version-d
- The version description for this new application version--version-tag
, -version-t
- The version tag for this new application versionsencha io create-version [options] [appName] \\\n [packagePath] \\\n [versionTag] \\\n [versionDescription] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nDeploys a previously created version of an Application to the cloud.
\n\nOnce an application has been deployed, it becomes publicly accessible.
\n\n--version-tag
, -v
- The version tag to deploysencha io deploy [options] [appName] \\\n [versionTag] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nLists all Applications which are accessible by this Developer (in the current\nTeam context).
\n\nIf the Developer is a member of multiple teams, they may have to switch Team\ncontexts to see all of the Applications to which they have access.
\n\nsencha io list-apps [username] \\\n [password] \\\n [teamName]\n
\n\nLists all the Authentication Groups to which this Developer currently has\naccess.
\n\nIf the Developer is a member of multiple teams, they may have to switch Team\ncontexts to see all of the Authentication Groups to which they have access.
\n\nsencha io list-groups [username] \\\n [password]\n
\n\nLists all of the currently uploaded versions of an Application in the system.
\n\nsencha io list-versions [appName] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nSets an Authentication Group's configuration.
\n\nAcceptible values for Authentication Method are senchaio (which is on by\ndefault), facebook, and twitter.
\n\nIn order to use facebook or twitter, Application Keys and Secrets must be\nobtained for you application with those services, and then be provided as the\nfinal parameters of this command.
\n\n--auth-method
, -au
- The auth method to set--enabled
, -e
- true/false, to enable the auth method--group-name
, -g
- The group name to set--key
, -k
- key for twitter/facebook auth--secret
, -s
- secret for twitter/facebook authsencha io set-group-auth [options] [groupName] \\\n [authMethod] \\\n [enabled] \\\n [username] \\\n [password] \\\n [key] \\\n [secret]\n
\n\nUndeploys a previously deployed version of an Application.
\n\nOnce this has been done, the application will no longer be publicly available.
\n\n--version-tag
, -v
- The version tag to undeploysencha io undeploy [options] [appName] \\\n [versionTag] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nThese commands gives you low level access to an io application's cloud hosting\nthrough an interface which ressembles a file system shell.
\n\nget
- Retrieve a remote file from the file systemls
- List all files in the file system for the supplied pathput
- Upload a file to the remote filesystemrm
- Remove a file or directory from the file systemRetrieves a remote file from an Application's filesystem in Sencha io.
\n\nsencha iofs get [appName] \\\n [path] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nLists the contents of a remote path in an Application's Sencha Io hosting.
\n\nsencha iofs ls [appName] \\\n [path] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nUploads a local file to a remote path in an Application's Sencha Io hosting.
\n\n--content-type
, -c
- The MIME content type of the file to be uploaded--local-path
, -l
- The local path of the file to be uploadedsencha iofs put [options] [appName] \\\n [path] \\\n [localPath] \\\n [contentType] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nRemoves a remote directory or file from an Application's remote Sencha Io\nhosting.
\n\nsencha iofs rm [appName] \\\n [path] \\\n [username] \\\n [password] \\\n [teamName]\n
\n\nThis command loads and executes the specified JavaScript source file or files.
\n\nsencha js file.js[,file2.js,...] [arg1 [arg2 ...] ]\n
\n\nThe first argument to this command is the file or files to execute. If there\nare multiple files, separate them with commas. In addition to the command line\ntechnique of specifying files, this command also recognizes the following\ndirective:
\n\n//@require ../path/to/source.js\n
\n\nThis form of require
directive uses a relative path based on the file that\ncontains the directive. Any given file will only be executed once, in much the\nsame manner as the compiler.
A primitive console
object with the following methods is provided to the\nJavaScript execution context:
log
debug
info
warn
error
dir
trace
time
/ timeEnd
Arguments beyond the first can be accessed in JavaScript with the global $args
\narray. The current directory can be accessed with $curdir
.
The Sencha Cmd object can be accessed with sencha
. This object has a version
\nproperty and a dispatch
method.
if (sencha.version.compareTo('3.0.0.210') < 0) {\n console.warn('Some message');\n} else {\n // dispatch any command provided by Cmd:\n sencha.dispatch([ 'app', 'build', $args[1] ]);\n}\n
\n\nBeyond the above, the executing JavaScript has full access to the JRE using\nthe importPackage
and importClass
methods.
For example:
\n\nimportPackage(java.io);\n\nvar f = new File('somefile.txt'); // create a java.io.File object\n
\n\nFor further details on the JavaScript engine provided by Java, consult the\nJava Scripting guide:
\n\nhttp://docs.oracle.com/javase/6/docs/technotes/guides/scripting/programmer_guide/index.html
\n\nsencha js String \\\n String[]...\n
\n\nThis category provides commands to manage application manifests.
\n\ncreate
- Generate a list of metadata for all classes found in the given directoriesThis command generates a list of metadata for all classes.
\n\n--output-path
, -o
- The file path to write the results to in JSON format.--path
, -p
- The directory path(s) that contains all classessencha manifest create [options] output-path\n
\n\nThese commands manage packages in the local repository.
\n\nThese commands are not typically used directly because application requirements\nare automatically used by sencha app build
and sencha app refresh --packages
\nto handle these details.
The most common commands needed to use packages are those that connect your\nlocal package repository to remote repositories. By default, the local repo has\none remote repository defined that points at Sencha's package repository.
\n\nTo add, remove or display these connections see:
\n\nsencha help package repo\n
\n\nWhen authoring packages for others to use in their applications, however, these\ncommands are involved. In particular, you must first initialize your local\npackage repository. This is because the local repository is automatically\ninitialized \"anonymously\". In this state, the local repository can only be used\nto retrieve and cache other packages. To create and publish packages, the local\nrepository must be initialized with a name and an optional email address.
\n\nThis name is not required to be globally unique, but it is a good idea to use a\nname that is unique and meaningful as a package author.
\n\nsencha repository init -name \"My Company, Inc.\"\n\nsencha repository init -name mySenchaForumId\n
\n\nFor details see:
\n\nsencha help repository init\n
\n\nrepository
- Manage local repository and remote repository connectionsadd
- Adds a package file (.pkg) to the local repositorybuild
- Builds the current packageextract
- Extracts the contents of a package to an output folderget
- Get a package from a remote repositorylist
- Lists packages in the repositoryremove
- Removes a package from the local repositoryupgrade
- Upgrades the current pacakgeAdds a new package file (\"*.pkg\"
) to the local repository. These packages will\nbe signed automatically if their creator
property matches the name
associated\nwith the local repository.
Once a package is added to the local repository, any repository that points to\nthis repository as a remote repository will be able to download the package.
\n\nThe sencha package build
process generates an appropriate \".pkg\"
file in the\nworkspace.build.dir
.
sencha package add pkgFile\n
\n\npkgFile
- The path to the package file (e.g., path/file.pkg)This command invokes the build process for the current package. Similar to an\napplication and sencha app build
, this command builds the current package (as\ndefined by the current folder).
sencha package build\n
\n\n--clean
, -c
- Remove previous build output prior to executing buildsencha package build [options] \n
\n\nThis command extracts a package or packages from the repository. If necessary\nthe packages will be downloaded from remote repositories and cached locally for\nfuture use.
\n\nNOTE:
This is not
typically executed manually but is handle automatically\nas part of the build process based on the \"requires\" found in \"app.json\"
and/or\n\"package.json\"
.
To extract a package named \"foo\" at version \"1.2\" to a specified location:
\n\nsencha package extract -todir=/some/path foo@1.2\n
\n\nThis will create \"/some/path/foo\"
. To recursively extract packages required\nby \"foo\", you would do this:
sencha package extract -recurse -todir=/some/path foo@1.2\n
\n\nWhen complete, \"foo\" and all of its required packages will reside in the folder\nspecified.
\n\nNOTE:
It is recommended to use -todir
and allow the package name to be used\nas the immediate subdirectory of that folder. The -outdir
option allows you to\nstrip off this directory but prevents recursive extraction as a result.
--clean
, -c
- Delete any files in the output folder before extracting--force
, -f
- Ignore local copy and fetch from remote repository--outdir
, -o
- The output folder for the extracted package contents--recurse
, -r
- Also get all required packages recursively--todir
, -t
- The output folder for the extracted package foldersencha package extract [options] packages...\n
\n\npackages
- The names/versions of the packages to extractThis command ensures that a specified package is locally available. This does\nnot
extract the package to a particular location, but rather, enables apps or\nother packages to get the package from the local repository (that is, without\ndownloading it).
For example, to ensure that \"foo\"
and \"bar\"
are available locally:
sencha package get foo bar\n
\n\nTo get all packages required by those specified packages:
\n\nsencha package get -recursive foo bar\n
\n\n--force
, -f
- Ignore local copy and (re)fetch from remote repository--recurse
, -r
- Also get all required packages recursivelysencha package get [options] packages...\n
\n\npackages
- One or more packages/versions to fetch locallyThis command lists packages in the repository. To list available packages\nsimply execute:
\n\nsencha package list\n
\n\nTo list locally available packages (no download required), do this:
\n\nsencha package list .\n
\n\nOtherwise, you can specify the names of package repositories to list:
\n\nsencha package list sencha\n
\n\nThe above will list the contents of the Sencha Cmd Package Repository.
\n\nsencha package list names...\n
\n\nnames
- The repos to list (blank for all, or remote names or \".\" for local)Removes one or more packages from the local repository.
\n\nRemoves version 1.2 of the package \"foo\":
\n\nsencha package remove foo@1.2\n
\n\nRemove all versions of \"foo\"
\n\nsencha package remove foo@...\n
\n\nsencha package remove packageNames...\n
\n\npackageNames
- One or more packages/versions to removeThese commands manage the local repository and its connections to remote\nrepositories.
\n\nThe primary role of the local repository is as a cache of packages that it\ndownloads from one or more specified remote repositories. By default, Sencha\nCmd adds the Sencha package repository as a remote repository. Using these\ncommands you can manage these connections.
\n\nThis command adds a remote repository connection named \"foo\"
:
sencha repo add foo http://coolstuff.foo/packages\n
\n\nFollowing this command, any packages contained in this repository will be\navailable. Typically these packages are used by adding their name (and possibly\nversion) to your application's \"app.json\"
in its requires
array.
{\n requires: [\n 'cool-package@2.1'\n ]\n}\n
\n\nThen:
\n\nsencha app build\n
\n\nThe above addition will require version 2.1 of \"cool-package\"
. The remote\nrepository added above will be checked for this package, and if found, it is\ndownloaded to the local repository and cached there as well as extracted to\nyour app's\"packages/cool-package\"
folder and automatically integrated in to\nyour build.
To author packages for others to use in their applications, you will need to\ninitialize your local repository with your name:
\n\nsencha repo init -name \"My Company, Inc.\"\n
\n\nSee these for more details:
\n\nsencha help package\nsencha help repo init\n
\n\nadd
- Add a remote repository connectioninit
- Initializes the local package repositorylist
- List remote repository connectionsremove
- Remove a remote repository connectionshow
- Show details for a repositorysync
- Clears caches to force refetching for a remote repositoryAdds a remote repository connection. Once added, packages from that repository\nwill be available to applications for use.
\n\nsencha repo add foo http://foo.bar/pkgs\n
\n\n--address
, -a
- The address (or URL) for the remote repository--name
, -n
- The name for the remote connectionsencha package repository add [options] name \\\n address\n
\n\nInitializes the local repository. The local repository is used to cache local\ncopies of packages (potentially for multiple versions).
\n\nNOTE:
This step is not typically necessary because the local repository is\nautomatically initialized in \"anonymous\" mode. This command is needed only if\nyou want to publish packages for others to use in their application. To publish\npackages you must initial the local repository and provide a name:
sencha repository init -name \"My Company, Inc.\" -email me@foo.com\n
\n\nBeyond initializing the repository file structures, this command also generates\na public/private key pair and stores these in the local repository. The private\nkey is used to sign packages added to this local repository.
\n\nFor details on adding packages:
\n\nsencha help package add\n
\n\nPackages added to the local repository with a creator
property equal to the\nname given to sencha repository init
will be signed using the private key\nstored in the local repository.
In this release of Sencha Cmd, these signatures are only used to test package\nintegrity. You can backup this key if desired, but a new key can be regenerated\nby running sencha repo init
at any time. In future versions it may be more\nimportant to backup your private key.
Making the local package repository available as a remote repository for others\nto access requires some knowledge of the disk structure of the repository. By\ndefault, Sencha Cmd creates the local repository adjacent to its installation\nfolder. For example, given the following location of Sencha Cmd:
\n\n/Users/myself/bin/Sencha/Cmd/3.1.0.200/\n
\n\nThe local respository is located at:
\n\n/Users/myself/bin/Sencha/Cmd/repo\n
\n\nThis is to allow your local repository to be used by newer versions of Sencha\nCmd. The folder to publish to others as an HTTP URL is:
\n\n/Users/myself/bin/Sencha/Cmd/repo/pkgs\n
\n\nIMPORTANT:
Do NOT
expose the parent folder of \"pkgs\"
- that folder holds\nprivate information (such as your private key). Further, Sencha Cmd will not\nrecognize the structure as a valid remote repository.
If you want to host the repository on a public server, simply copy the \"pkgs\"
\nfolder to a web server and share the HTTP address.
--email
, -em
- The email address for the owner of the local repository--expiration
, -ex
- The number of years before the key pair becomes invalid--keybits
, -k
- The number of bits for the public/private key pair--name
, -n
- The name for the owner of the local repositorysencha package repository init [options] \n
\n\nLists all remote repository connections.
\n\nsencha package repository list \n
\n\nRemove a remote repository from the local repository's list of remote\nrepositories. For example, if a remote was previously added:
\n\nsencha repo add foo http://foo.bar/pkgs\n
\n\nThis command will remove it:
\n\nsencha repo remove foo\n
\n\nNOTE:
This command does not remove packages that you may have downloaded from\nthis remote as they are now cached in the local repository.
--name
, -n
- The name for the remote connectionsencha package repository remove [options] name\n
\n\nShows information about a remote repository.
\n\nTo show information about the local repository:
\n\nsencha repo show .\n
\n\nTo show information about a specific remote repository:
\n\nsencha repo show some-remote\n
\n\nThe name given should match the name previously given to:
\n\nsencha repo add some-remote ...\n
\n\n--all
, -a
- Include all details about the repositorysencha package repository show [options] names...\n
\n\nnames
- The name(s) of remote repositories (or \".\" for local)Forces (re)synchronization with a remote repository catalog. Normally this is\ndone periodically and does not need to be manually synchronized. This command\nmay be needed if there something known to have been added to a remote repo but\nhas not yet shown up in the catalog on this machine.
\n\nsencha repo sync someremote\n
\n\nTo resynchronize with all remote repositories:
\n\nsencha repo sync\n
\n\n--name
, -n
- The name for the remote connection (blank for all)sencha package repository sync [options] [name]\n
\n\nUpgrades the current package to a newer SDK or Sencha Cmd version.
\n\nThis command must be run from the desired package's folder.
\n\nsencha package upgrade \n
\n\nThese commands manage the local repository and its connections to remote\nrepositories.
\n\nThe primary role of the local repository is as a cache of packages that it\ndownloads from one or more specified remote repositories. By default, Sencha\nCmd adds the Sencha package repository as a remote repository. Using these\ncommands you can manage these connections.
\n\nThis command adds a remote repository connection named \"foo\"
:
sencha repo add foo http://coolstuff.foo/packages\n
\n\nFollowing this command, any packages contained in this repository will be\navailable. Typically these packages are used by adding their name (and possibly\nversion) to your application's \"app.json\"
in its requires
array.
{\n requires: [\n 'cool-package@2.1'\n ]\n}\n
\n\nThen:
\n\nsencha app build\n
\n\nThe above addition will require version 2.1 of \"cool-package\"
. The remote\nrepository added above will be checked for this package, and if found, it is\ndownloaded to the local repository and cached there as well as extracted to\nyour app's\"packages/cool-package\"
folder and automatically integrated in to\nyour build.
To author packages for others to use in their applications, you will need to\ninitialize your local repository with your name:
\n\nsencha repo init -name \"My Company, Inc.\"\n
\n\nSee these for more details:
\n\nsencha help package\nsencha help repo init\n
\n\nadd
- Add a remote repository connectioninit
- Initializes the local package repositorylist
- List remote repository connectionsremove
- Remove a remote repository connectionshow
- Show details for a repositorysync
- Clears caches to force refetching for a remote repositoryAdds a remote repository connection. Once added, packages from that repository\nwill be available to applications for use.
\n\nsencha repo add foo http://foo.bar/pkgs\n
\n\n--address
, -a
- The address (or URL) for the remote repository--name
, -n
- The name for the remote connectionsencha repository add [options] name \\\n address\n
\n\nInitializes the local repository. The local repository is used to cache local\ncopies of packages (potentially for multiple versions).
\n\nNOTE:
This step is not typically necessary because the local repository is\nautomatically initialized in \"anonymous\" mode. This command is needed only if\nyou want to publish packages for others to use in their application. To publish\npackages you must initial the local repository and provide a name:
sencha repository init -name \"My Company, Inc.\" -email me@foo.com\n
\n\nBeyond initializing the repository file structures, this command also generates\na public/private key pair and stores these in the local repository. The private\nkey is used to sign packages added to this local repository.
\n\nFor details on adding packages:
\n\nsencha help package add\n
\n\nPackages added to the local repository with a creator
property equal to the\nname given to sencha repository init
will be signed using the private key\nstored in the local repository.
In this release of Sencha Cmd, these signatures are only used to test package\nintegrity. You can backup this key if desired, but a new key can be regenerated\nby running sencha repo init
at any time. In future versions it may be more\nimportant to backup your private key.
Making the local package repository available as a remote repository for others\nto access requires some knowledge of the disk structure of the repository. By\ndefault, Sencha Cmd creates the local repository adjacent to its installation\nfolder. For example, given the following location of Sencha Cmd:
\n\n/Users/myself/bin/Sencha/Cmd/3.1.0.200/\n
\n\nThe local respository is located at:
\n\n/Users/myself/bin/Sencha/Cmd/repo\n
\n\nThis is to allow your local repository to be used by newer versions of Sencha\nCmd. The folder to publish to others as an HTTP URL is:
\n\n/Users/myself/bin/Sencha/Cmd/repo/pkgs\n
\n\nIMPORTANT:
Do NOT
expose the parent folder of \"pkgs\"
- that folder holds\nprivate information (such as your private key). Further, Sencha Cmd will not\nrecognize the structure as a valid remote repository.
If you want to host the repository on a public server, simply copy the \"pkgs\"
\nfolder to a web server and share the HTTP address.
--email
, -em
- The email address for the owner of the local repository--expiration
, -ex
- The number of years before the key pair becomes invalid--keybits
, -k
- The number of bits for the public/private key pair--name
, -n
- The name for the owner of the local repositorysencha repository init [options] \n
\n\nLists all remote repository connections.
\n\nsencha repository list \n
\n\nRemove a remote repository from the local repository's list of remote\nrepositories. For example, if a remote was previously added:
\n\nsencha repo add foo http://foo.bar/pkgs\n
\n\nThis command will remove it:
\n\nsencha repo remove foo\n
\n\nNOTE:
This command does not remove packages that you may have downloaded from\nthis remote as they are now cached in the local repository.
--name
, -n
- The name for the remote connectionsencha repository remove [options] name\n
\n\nShows information about a remote repository.
\n\nTo show information about the local repository:
\n\nsencha repo show .\n
\n\nTo show information about a specific remote repository:
\n\nsencha repo show some-remote\n
\n\nThe name given should match the name previously given to:
\n\nsencha repo add some-remote ...\n
\n\n--all
, -a
- Include all details about the repositorysencha repository show [options] names...\n
\n\nnames
- The name(s) of remote repositories (or \".\" for local)Forces (re)synchronization with a remote repository catalog. Normally this is\ndone periodically and does not need to be manually synchronized. This command\nmay be needed if there something known to have been added to a remote repo but\nhas not yet shown up in the catalog on this machine.
\n\nsencha repo sync someremote\n
\n\nTo resynchronize with all remote repositories:
\n\nsencha repo sync\n
\n\n--name
, -n
- The name for the remote connection (blank for all)sencha repository sync [options] [name]\n
\n\nThis category contains low-level commands for managing themes. Typically these\noperations are handled by sencha app build
and/or sencha package build
.
build
- Builds a custom theme from a given pagecapture
- Capture an image and slicer manfiest for a themeslice
- Generates image slices from a given image directed by a JSON manifestThis command will build the specified theme's image sprites.
\n\nIMPORTANT
: This command should only be used for Ext JS 4.1 applications. For\nExt JS 4.2 applications, themes are now packages
and should be managed using\nthe sencha package build
process.
--environment
, -en
- The build environment (e.g., production or testing)--output-path
, -o
- The destination path for the sliced images--page
, -p
- The page to slice--theme-name
, -t
- The name of the theme to buildsencha theme build [options] [theme-name] \\\n [environment]\n
\n\nThis command will capture an image and slice manifest for a specified page.
\n\nIt is rarely necessary to call this command directly as it is part of the theme\nbuild process. In Ext JS 4.2 applications or theme packages, this command is\ncalled by the build script's slice
step. In Ext JS 4.1 applications this is\ncalled for each application theme or directly by the 'sencha theme build`\ncommand.
For example, this is roughly the command performed by the slice
step for a\ntheme package:
sencha theme capture -page sass/example/theme.html \\\n -image build/theme-capture.png \\\n -manifest build/theme-capture.json\n
\n\nOnce the image and slicer manifest are produced, the sencha fs slice
command\nextracts the background images and sprites required for Internet Explorer.
--image-file
, -i
- The output image (e.g. \"theme-capture.png\")--manifest
, -m
- The output slice manifest (e.g. \"theme-capture.json\")--page
, -p
- The page to load for capturing theme contentssencha theme capture [options] \n
\n\nThis command performs image slicing and manipulation driven by the contents of\na JSON manifest file. The manifest file contains an array of image area\ndefinitions that further contain a set of \"slices\" to make.
\n\nThis file and the corresponding image are typically produced for a Theme as\npart of the theme package build. For details on this process, consult this\nguide:
\n\nhttp://docs.sencha.com/ext-js/4-2/#!/guide/command_slice
\n\n--format
, -f
- The image format to save - either \"png\" or \"gif\" (the default)--image
, -i
- The image to slice--manifest
, -m
- The slicer manifest (JSON) file--out-dir
, -o
- The root folder to which sliced images are written--quantized
, -q
- Enables image quantization (default is true)--tolerate-conflicts
, -t
- Tolerate conflicts in slice manifestsencha theme slice [options] \n
\n\nThis command downloads and installs the current version of Sencha Cmd. Or you\ncan specify the version you want to install as part of the command.
\n\nThe following command downloads and installs the current version of Sencha Cmd:
\n\nsencha upgrade\n
\n\nThis command downloads a particular version:
\n\nsencha upgrade 3.0.2.288\n
\n\nIf the version requested is the already installed then this command will, by\ndefault, do nothing. This can be forced using --force
:
sencha upgrade --force\n
\n\nIf the version requested is the version in the PATH
, the command will exit\nwith a message saying that the current version cannot be upgraded. In this case\nthe --force
option is ignored.
--beta
, -b
- Check for the latest beta or RC version (vs stable release)--check
, -c
- Only check for an upgrade but do not install it--force
, -f
- Force a (re)install even if the version is already installedsencha upgrade [options] [version=\"\"]\n
\n\nThis command display the location of Sencha Cmd.
\n\nsencha which\nC:\\Users\\Me\\bin\\Sencha\\Cmd\\3.1.0.220\n
\n\n--output
, -o
- Name of an output property file to write the location as a property--property
, -p
- Name of the property to write to the output property file for the locationsencha which [options] \n
\n"});