Deploy Sencha Cmd Package Repository to http://deftjs.org/

[superstructor]

Ref http://docs.sencha.com/extjs/4.2.1/#!/guide/command_package_authoring-section-hosting-a-package-repository

Basically involves

1. sencha package build from packages/deft directory
2. add the package to your local repository sencha package add build/deft/deft.pkg (in the workspace build directory NOT the package build directory).
3. make a copy of your local repository to the http://deftjs.org web server under a path like /packages so e.g. sencha repo add -address http://deftjs.org/packages -name deft would work

Thoughts ?

[johnyanarella]

The Sencha docs seem lacking on how we host multiple versions in our repository. Have you seen anything along those lines?

[johnyanarella]

Ah, I see now - looks like we mirror the pkgs directory illustrated in the Local Repository section.

http://docs.sencha.com/extjs/4.2.1/#!/guide/command_package_authoring

[superstructor]

Yes correct, from what I understand pkgs/* in the repo becomes http://deftjs.org/packages/*

[superstructor]

Appears to be working:

$ sencha repo add -address http://packages.deftjs.org -name deft 
Sencha Cmd v3.1.2.342
[INF] Adding remote "deft"
[INF] Remote "deft" added

$ sencha repo show --all deft
Sencha Cmd v3.1.2.342
[INF] Remote repository "deft" (owner: Deft JS)
[INF]    Packages: 1
[INF]    Expires: Tue Jun 26 12:00:00 NZST 2018
[INF]    Type: HTTP
[INF]    Address: http://packages.deftjs.org/
[INF]    Priority: 0

$ sencha package list deft     
Sencha Cmd v3.1.2.342
[INF] Listing of deft catalog
[INF]    Package deft
[INF]       *0.9.0*
[INF]    1 package(s)

And from a package directory that depends on DeftJS via the requires array:

$ sencha package build
[INF] Including code package deft for build
Sencha Cmd v3.1.2.342
[INF] 
[INF] init-plugin:
[INF] 
[INF] init-package-plugin:
[INF] 
[INF] package-build:
[INF] Including code package deft for build

And from an ExtJS application directory that depends on DeftJS via the requires array:

$ sencha app build                 
[INF] Including theme package ext-theme-classic for app.theme=ext-theme-classic build
[INF] Including code package deft for build
<cut>
[INF] Loading classpath entry /var/www/sencha/ext-4.2.1.883/src
[INF] Loading classpath entry /var/www/sencha/ext-4.2.1.883/packages/ext-theme-base/overrides
[INF] Loading classpath entry /var/www/sencha/ext-4.2.1.883/packages/ext-theme-base/src
[INF] Loading classpath entry /var/www/sencha/ext-4.2.1.883/packages/ext-theme-neutral/overrides
[INF] Loading classpath entry /var/www/sencha/ext-4.2.1.883/packages/ext-theme-neutral/src
[INF] Loading classpath entry /var/www/sencha/ext-4.2.1.883/packages/ext-theme-classic/overrides
[INF] Loading classpath entry /var/www/sencha/ext-4.2.1.883/packages/ext-theme-classic/src
[INF] Loading classpath entry client-side/packages/deft/overrides
[INF] Loading classpath entry client-side/packages/deft/src
<cut>

And from a Touch application directory that depends on DeftJS via the requires array:

$ sencha app build
[INF] Including code package deft for build
<cut>
[INF] Loading classpath entry /var/www/sencha/touch-2.2.1/src
[INF] Loading classpath entry client-side/packages/deft/overrides
[INF] Loading classpath entry client-side/packages/deft/src