digitarald / d2g Goto Github PK

probably need a build step so that each instance of the d2g service has a public/private keypair for its domain. For use in signing packaged apps on the server AND verifying those signatures on the device at install time.

As a developer, I want to not care about version bumping, so I can make changes that are relevant to me.

We should append the epoch timestamp to the version number in the manifest.

We should also be careful to check that the client does validation of the mini-manifest's version number. If it does, we'll need to re-write the manifest to match the mini-manifest's generated version number.

Check at npm start or npm install if the cert exists in config/.

For bonus points: check for the existence of the cert in mongo.

FxOS updates are based on HTTP caching and E-Tags.

Derive the E-Tags from the MongoDB's ids.

We should provide an API to the frontend code which updates Monogo as well as S3.

• generate a mini-manifest from the zip file.
• mozApps.installPackage()

after creating a keypair for an instance of the service, we need to simplify as much as possible the installation of private keys

dotCloud / docker is the new hotness for deploying code.

We should do that for d2g server.

Python script used by Marketplace: https://github.com/mozilla/signing-clients/blob/master/signing_clients/apps.py

Step 1:

• Command-line node script loads a zip file
• Signs it
• Saves the signed packaged back

Step 2:

• use S3

version.js has commented out using Buffer.

That is because we are getting

/home/ozten/d2g/node_modules/mongoose/lib/schema.js:362
    throw new TypeError('Undefined type at `' + path +
          ^
TypeError: Undefined type at `_signedPackage`
  Did you try nesting Schemas? You can only nest using refs or arrays.
    at Function.Schema.interpretAsType (/home/ozten/d2g/node_modules/mongoose/lib/schema.js:362:11)
    at Schema.path (/home/ozten/d2g/node_modules/mongoose/lib/schema.js:305:29)
    at Schema.add (/home/ozten/d2g/node_modules/mongoose/lib/schema.js:217:12)
    at new Schema (/home/ozten/d2g/node_modules/mongoose/lib/schema.js:73:10)
    at Object.<anonymous> (/home/ozten/d2g/models/version.js:3:21)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

If we generate a version number on behalf of the developer, we should update the file system and re-package the app.