Atmosphere

How I imagine it working

Everything is git based. To define a version we need these pieces:

1. Package name

2. A version number

3. A repo

4. A commit that we associate with the specified version number (mrt publish can grab this from the local repo using git's rev-parse)

5. A list of deps

Minimum Smart JSON for Publishing

{
  "name": "test-pkg",
  "description": "A test package!",
  "homepage": "https://github.com/possibilities/atmosphere-test-pkg",
  "author": "Mike Bannister <[email protected]> (http://po.ssibiliti.es)",
  "version": "0.0.5",
  "git": "https://github.com/possibilities/atmosphere-test-pkg.git"
}

What we save on the server

	{
	    "author": "Mike Bannister  (http://po.ssibiliti.es)",
	    "createdAt": "2012-07-31T04:39:20.340Z",
	    "description": "A test package!",
	    "git": "https://github.com/possibilities/atmosphere-test-pkg.git",
	    "homepage": "https://github.com/possibilities/atmosphere-test-pkg",
	    "latest": "0.0.5",
	    "name": "test-pkg",
	    "updatedAt": [
	        "2012-07-31T04:39:20.340Z",
	        "2012-07-31T04:43:11.253Z",
	        "2012-07-31T04:44:10.705Z",
	        "2012-07-31T04:49:15.927Z"
	    ],
	    "versions": [
	        {
	            "version": "0.0.4",
	            "packages": null,
	            "createdAt": "2012-07-31T04:39:20.340Z",
	            "updatedAt": [
	                "2012-07-31T04:39:20.340Z"
	            ]
	        },
	        {
	            "version": "0.0.5",
	            "packages": null,
	            "createdAt": "2012-07-31T04:43:11.253Z",
	            "updatedAt": [
	                "2012-07-31T04:43:11.253Z",
	                "2012-07-31T04:44:10.705Z",
	                "2012-07-31T04:49:15.927Z"
	            ]
	        }
	    ]
	}