Update for heroku platform about meteor-security

[aldeed]

I can't think of any reason why this package would require building for multiple servers. It's fairly simple and doesn't depend on any binary npm packages.

[aldeed]

@aaronjudd did you get the notice about needing to build for all architectures when you published the last release?

[aaronjudd]

no, no notice. I was expecting that, but I don't always get one unless I have NPM in the package.

[aaronjudd]

meteor show ongoworks:security --ejson shows

      "name": "ongoworks:security",
      "version": "1.2.0",
      "description": "A Meteor package that provides a simple, logical, plain language API for defining write security on your MongoDB collections. Wraps the core allow/deny security.",
      "summary": "Logical security for client-originated MongoDB collection operations",
      "git": "https://github.com/ongoworks/meteor-security.git",
      "publishedBy": "ongoworks",
      "publishedOn": {
        "$date": 1435018090809
      },
      "installed": false,
      "architecturesOS": [
        "os"
      ]
    },

which I presume means "all OS" because when you build each machine it gets a listing in the architecturesOS object. Previous versions show the same architecture info.

Just to test, I did meteor admin get-machine os.windows.x86_32 and meteor publish-for-arch ongoworks:[email protected] which responds (same for all arch)

While publishing package build for ongoworks:security:
error: Cannot override existing build