1. #1
    Sencha User
    Join Date
    Mar 2011
    Vote Rating
    incutonez is on a distinguished road


    Default Maintaining a remote package repository using Sencha Cmd

    I'm trying to understand how to use the proper commands and flow of creating/updating a remote package repository... using Sencha Cmd v5.1.2.52. This is my current flow of updating a package that is used in one of my apps:
    1. (in package dir) make appropriate changes
    2. (in package dir) change package.json version number (if this doesn't get changed, my app won't pick up the changes)
    3. (in package dir) sencha package build
    4. (in workspace that contains package dir/build/<my_package>) sencha package add <my_package>.pkg (adds to local repo)
    5. cp bin/Sencha/Cmd/repo/pkgs/ to remote repo
    6. (in app dir, separate from above workspace) sencha app refresh -packages
    7. (in app dir) sencha app build
    First question... am I doing anything weird? Are there any shortcuts I could take? Second question... is this how others are doing it? I couldn't figure out a good way of doing it from the docs. I found a couple of threads (here and here) with similar issues, but they're about a year old, so I was hoping there'd be an update.

    Step 2 seems strange that I HAVE to update the version number, and step 4 seems strange as well. Ideally, I'd have my package workspace as saved off in SVN, so I'd do a package build, and the package hosting structure would be added to my workspace dir, which is where I basically could do my hosting from SVN... that would cut out steps 4 and 5. I realize a package refresh is necessary in the app that is using it, but having to update the version is something I know I'll forget to do... so is there a way to just do a "hard refresh?"

  2. #2
    Sencha Premium Member
    Join Date
    Feb 2012
    Hillsborough, NC
    Vote Rating
    worthlutz is a jewel in the rough worthlutz is a jewel in the rough worthlutz is a jewel in the rough



    I'm just embarking on this journey.

    I see no replies so I'm assuming the process described is the way to go.

    Any updates? Is this really how it is done?

Similar Threads

  1. Maintaining a remote repository for packages
    By Fredric Berling in forum Sencha Cmd
    Replies: 8
    Last Post: 16 Sep 2014, 4:31 PM
  2. Package remote Repository
    By k_cire0426 in forum Sencha Cmd
    Replies: 2
    Last Post: 23 Oct 2013, 1:48 PM
  3. Error: The package command has moved to 'sencha app package'
    By Luis Miguel in forum Sencha Architect 2.x: Help & Discussions
    Replies: 4
    Last Post: 6 Feb 2013, 2:05 PM
  4. Can't package Sencha Touch app as a local android package
    By edwin032602 in forum Sencha Touch 2.x: Q&A
    Replies: 4
    Last Post: 27 Jul 2012, 2:52 AM
  5. Remote Sort, Remote Group, Remote Paging events.
    By FCTim in forum Ext 3.x: Help & Discussion
    Replies: 2
    Last Post: 15 Jun 2010, 10:05 AM

Thread Participants: 1