New Charm: npm-app

[Alan Meekins]

Just following the directions for charm ingestion at: https://jujucharms.com/docs/1.25/charms-bundles to get my package included in the charm store.

https://code.launchpad.net/~alan-meekins/charms/trusty/npm-app/trunk

This charm is a fork of node-app which unlike node-app uses `npm start` to execute services in a way more in line with how npm packages are actually used.

[Review Queue (review-queue)]

This item has failed automated testing! Results available here http://juju-ci.vapour.ws:8080/job/charm-bundle-test-aws/3955/

[Review Queue (review-queue)]

This item has failed automated testing! Results available here http://juju-ci.vapour.ws:8080/job/charm-bundle-test-lxc/3910/

[Cory Johns (johnsca)]

Alan,

Thank you for your contribution! If this is the more correct way of starting the node apps, would you prefer to submit this as a Merge Proposal against node-app (https://code.launchpad.net/~charmers/charms/precise/node-app/trunk) instead? If you wish to submit this as a replacement, is there a significant reason to change the name from node-app to npm-app?

Additionally, if you only want a charm to be available for deployment from the store, you can publish it in your own namespace (see the instructions for the new publish workflow here: https://jujucharms.com/docs/devel/authors-charm-store). It would then be available for deploy with:

    juju deploy cs:~alan-meekins/trusty/npm-app

Submitting a charm for review is only required if you then want it to be promulgated to the top-level namespace, i.e., cs:trusty/npm-app

[Pen Gale (pengale)]

Hi Alan,

Please let us know how you'd like to proceed, per Cory's comment above.