{"_id":"site-manager-baseline","_rev":"65-42fc056f47a518a9e3cb6c68c8bb2344","name":"site-manager-baseline","description":"Client-side UI for the Site-Manager applications","dist-tags":{"latest":"0.10.3"},"versions":{"0.0.1":{"name":"site-manager-baseline","version":"0.0.1","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"git://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"node-uuid":"*","socket.io":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"email":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.5.0 < 0.7.0"},"_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"_id":"site-manager-baseline@0.0.1","optionalDependencies":{},"_engineSupported":true,"_npmVersion":"1.1.24","_nodeVersion":"v0.6.19","_defaultsLoaded":true,"dist":{"shasum":"3ad210724bf3524c38c17724c6bbe11f9261befb","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.0.1.tgz","integrity":"sha512-hL+PgP3D0YobCTMKKiNpOwZBa5kH9XCC6QWVZ+mGK+yAdH/Xub5VDy3RZquMz080F3cITQDIp+NC784R99wYWg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC5e3dPwSfOQTUc550YuqL0fe2omGzN2MC+N6/VKVxLlQIhAKfehox5GdVNAMeYVIyRrU3fMPmb8SS/yHW54GHXHf0e"}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.1.0":{"name":"site-manager-baseline","version":"0.1.0","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"git://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"node-uuid":"*","socket.io":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"email":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.5.0 < 0.7.0"},"_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"_id":"site-manager-baseline@0.1.0","optionalDependencies":{},"_engineSupported":true,"_npmVersion":"1.1.24","_nodeVersion":"v0.6.19","_defaultsLoaded":true,"dist":{"shasum":"006916a055796747da1a2d45dc7e77c19ce36afe","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.1.0.tgz","integrity":"sha512-vDzD6E13VpLxb6PiVjamwEMF2EFsoQlNKXgsiQ4R8jih4wsfUCo/UbWjPn6PEJhbYVSuYZXIOWyt9gLogSWDAw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCM0slSR5Vr/zL4QiHZgxGn58DirS2WjKfgnBqSoQ7QQAIgUOyQbSKvgLwGB8Xh1y+y36GKy/mRhjtamUcm1aw6stA="}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.1.1":{"name":"site-manager-baseline","version":"0.1.1","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"node-uuid":"*","socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.5.0 < 0.7.0"},"_id":"site-manager-baseline@0.1.1","dist":{"shasum":"ad68a030001bd39c6e5c5a29900c2f960c74cfe3","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.1.1.tgz","integrity":"sha512-dVfqpeuPX1jpRuUP64wh+V9MH3wDTuXvnxtWtO39wD9ceWAiRlg9ww6Sk+SpjDDwPrBsoRFruBL+D4uElx3kng==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCFpsE6LOUUHD5XfOUTkykMRM0s6u/+b0ub34Wnar8Y6gIhAPaSlyOYxvjWMBcmhsOZvd7FF6UMKhnmhkIB2VIJu2jl"}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.1.2":{"name":"site-manager-baseline","version":"0.1.2","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"node-uuid":"*","socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.5.0 < 0.7.0"},"_id":"site-manager-baseline@0.1.2","dist":{"shasum":"a79ffa38d5e6faaf755777402c3c4d4f6e03eae9","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.1.2.tgz","integrity":"sha512-hDL1zYI+O3gEM7p7xDB20HKsF9+fz10DuT/iOcrPP2NJhzThcAYgKInJVP4UeAGN21JL6cgGMidWLWsf8TyIqA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDycrQVZUE2Qb4By1C2R3R499DDtSEb4h/7M31ue40RkAIhAOcxlhKcHHCXbw+EVN7XeJL6oEidIjBD9/j+yMvNomWe"}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.1.3":{"name":"site-manager-baseline","version":"0.1.3","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"node-uuid":"*","socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.5.0 < 0.9.0"},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","_id":"site-manager-baseline@0.1.3","dist":{"shasum":"e19d5e17867987d46e40ae59bcff5640f438527d","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.1.3.tgz","integrity":"sha512-FG2slHuJQdfNItRMnPuNq+dg0PUXz7zb3UcO5Dd9I4QA57scslYSvJCupDjgVl9r+oWVg4qAjjZGTipud995Gw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIHZ28+Ve+c2hpfR1vqxZ3xeyRRMhi+JHEnRePneF5oAdAiAVf5pxLm2tYG1hmYMLH3oOlN5fWr43hnQtT5XRoRzl0Q=="}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.1.5":{"name":"site-manager-baseline","version":"0.1.5","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"node-uuid":"*","socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.1.5","dist":{"shasum":"3bc0423f2d863d808744c8e0af764cbf8e15c767","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.1.5.tgz","integrity":"sha512-ujdxX+xDy4VlOy92Hu08+kqWiod6xpJwvCwPc+Llf9Ta18cVxKQ/5EydIqWLCsllG/fDhH2MCAGPbNiIF9FRpA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBdfqm2s8iUQkOBtzGQzs9SCmn3wOCl9GZMFuvUtQQGoAiALNwY3DFX+h+5RlOmeDr27DVGflAeyHVvikda0f8/CKg=="}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.2.0":{"name":"site-manager-baseline","version":"0.2.0","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"mongodb":"*","socket.io":"*","handlebars":"*","site-manager-bootstrap":"*","socket.io-mongo":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","_id":"site-manager-baseline@0.2.0","dist":{"shasum":"143e409afad9815467dd1dc150c88a692584ac7e","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.2.0.tgz","integrity":"sha512-yt6t152eDO2o32//ZsAplj/0BNziMb4BZLa6MnQ772F08L+5mg5+4aWovlo4J88XQQ0UImpRs2ARSoDh9cGjjQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIAefJOs+JoiT/PuutUdMH2T1iUY5Tr0k5fU9kwNttOltAiEAjtFHWB8JLehOhMDEb9s/j7hFVRL/3KLFYG6pyMA5oWs="}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.3.0":{"name":"site-manager-baseline","version":"0.3.0","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","_id":"site-manager-baseline@0.3.0","dist":{"shasum":"148a06eec41e59b3e66d9cb78bc65e5f335c71de","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.3.0.tgz","integrity":"sha512-tfrNJvsigC4L00kOY5KHcW63Q5/NvAG5RC2CuuF53qYqGqxXOuV/zRRFcRpKI1AyegfG4fpL7zluXCaFqUPaOA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDPPrkbpj0jjO+uBle2+pcvhfbg7wn5w4q8nZ3V+86cyQIhAL8S+nITq6gNKUz9o8CQhvDVUYAkDIGhft9+5PExGezV"}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.8.5":{"name":"site-manager-baseline","version":"0.8.5","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.8.5","readme":"ERROR: No README.md file found!","dist":{"shasum":"20ff8e2dd7e7788aac5c106fd37eb4976614397f","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.8.5.tgz","integrity":"sha512-UBOp+rmSa4d1DrBAYCEwH0/WaCqoX0DsmCfrP1F5YN2S2CrsUfzCHxvS6ZMyTAP9D+8aC2E/IJB1qtMyf5dh7Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGU004FNZ7wxopT56orNdBUAMThFfkjiACbQZFosIuUPAiEAzaH/Qvb8gt+0fJnTDLxs86W9OeBdIC6y7jTv8gvM2Fw="}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.8.6":{"name":"site-manager-baseline","version":"0.8.6","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.8.6","readme":"ERROR: No README.md file found!","dist":{"shasum":"59be5c640baafbed431984ead668f1af5bb66433","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.8.6.tgz","integrity":"sha512-ECamb9J6fkj3CgJaM8hZMO3DISlhqg3ttSFQz8gkjDt2tswPS9PGznejw8lVd2YwHKi97Ora5wO7dZ99evDD7w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC2OwuM8JcmfdvKkDUayShyiSPw4JLAw9rEDWK9SlPliAIhAOlz3l+TyD9t3k+uZ7YNt4Ei8YSNniXsakP6rkNpu2Sx"}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.8.8":{"name":"site-manager-baseline","version":"0.8.8","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.8.8","readme":"ERROR: No README.md file found!","dist":{"shasum":"822dedf987e018b7e7f555d64a31e2541a6fba9b","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.8.8.tgz","integrity":"sha512-xQhmdI7sC5aM6fWoSTKv8YXlk0UdaIJ7uU2M4TafrzjG2i3ojWuX55VZmR6+luTNkmtYeY4c/Xm6EnIqPlJZ5w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBIiCvFEUHuLdtOAVOtr1/9MkgYqpw5pWvkn5hg6oNz8AiAH2/j4PHS1hNztY3di+L/DqecsyROHAKg6oCst6kV8qg=="}]},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.8.9":{"name":"site-manager-baseline","version":"0.8.9","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.8.9","readme":"ERROR: No README.md file found!","dist":{"shasum":"69e3255d0a7254ac69e3d66950132ea5a0d7bbfc","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.8.9.tgz","integrity":"sha512-+sy/V8P9tYKeI1j3WdmElaMV5qUlEUme4P7LHhXUgFm8JmcRZtz/tYUxk1jOClDp0uIhK7p/8+2OU48ecWQW9Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDFtBAISfXG0J9D2swgijnfe6vE33Epx6SYDW+aK1AM+gIhAMANTAO3sQYFwKFUXOMZTqYzrKIBm3Iaazr66oYxbq4a"}]},"_npmVersion":"1.1.49","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.8.10":{"name":"site-manager-baseline","version":"0.8.10","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.8.10","readme":"ERROR: No README.md file found!","dist":{"shasum":"d05cec7e747c339c568597b91ca7d696489a4ced","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.8.10.tgz","integrity":"sha512-N9seyYv6YXACSSvs0goJQQOqh2Nu8c3ccoxRURos16+qtgO/jGK65oSRi0gLI1epE61VDrAOzaqpMGBE4vsv3Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIENZ9tRE5hgm30MlHIy7E3AEBuN2xsWnfecyN3j5jkoLAiEA4yvqJf0pK6iqHqIt8CHCxLLz8uYaijLgiIqz18G1Kd4="}]},"_npmVersion":"1.1.49","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.8.11":{"name":"site-manager-baseline","version":"0.8.11","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","_id":"site-manager-baseline@0.8.11","dist":{"shasum":"25f3d24ca4950e8c96aebd9dc5eb9be2264cea75","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.8.11.tgz","integrity":"sha512-SkrJc77OGWrazo1EWhIm3VR4Sjce26E81jlWwS44VCSmqnv65TVoEJoYyg/dFmIwJhr5/D8D13zP0a+0YXXnqg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHuPsH20WDJbObDrUHdP+AqVB6vfa2BPMrSCmvRGA699AiEAy42aQcBQsjpihD0taWmA0s3kVQarGRrMDHCTMytbGl4="}]},"_npmVersion":"1.1.49","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.8.12":{"name":"site-manager-baseline","version":"0.8.12","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.8.12","readme":"ERROR: No README.md file found!","dist":{"shasum":"7125f04087f50eeb3c7f40ddcf5c41004ccf0e6b","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.8.12.tgz","integrity":"sha512-p7NComU6kisKhW7RG6hvyq4/KXUKewXa8Jy+HmL1xL2hRH9Sd+UKTV2oGYQgBtF0vXyn8UKegIUehSLkINE3yA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDnkjg3HGYG1ZSoEVzcfQBim4Kp5V0UkpDrK+KOV9n6HwIgau0hzPL2kfxTpMb6GEcTNg51yofQcF5KwfER9TicQQQ="}]},"_npmVersion":"1.1.52","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.8.13":{"name":"site-manager-baseline","version":"0.8.13","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","site-manager-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.8.13","readme":"ERROR: No README.md file found!","dist":{"shasum":"33d9ca7ac51a59e63dd99eb18af45a728e04c493","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.8.13.tgz","integrity":"sha512-DrHNK55JYZenwoW3eo22yhvuj3g7jRRezrZQMDtTy6Wvt63/KmjLL1x719PxhPzXSaOrsbDrOGq0+a+l9FkQzg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDVU4m5pIcvUNRX6ShH1SnUAqkClSW7WdOOqcwIBkd+VQIgUX/ZU9dm7Egu8CXsa9POd6qWiiTLBxKi9rCR5iWCl7c="}]},"_npmVersion":"1.1.52","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.8.15":{"name":"site-manager-baseline","version":"0.8.15","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","jolira-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.8.15","readme":"ERROR: No README.md file found!","dist":{"shasum":"07a57adeb045bf4aa48157c71781ad497a9bfab6","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.8.15.tgz","integrity":"sha512-kJKRojAwQxb3hLHSo9naefRHtMuKbxQvWKNqknRmJKvhbuc9dWzXlXRILdFaGKKAaZAkDmjOnaXkdUtUP3Ytiw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCIVq/ktDl4ZEvTMK9p8S6f+aD4Saxm7zSkpcTpbGf/FwIgR7cIBPtEJS2pnc9pPyR+UaJfqAWUY98HZ1KMJekw0U4="}]},"_npmVersion":"1.1.59","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.9.1":{"name":"site-manager-baseline","version":"0.9.1","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","jolira-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"_id":"site-manager-baseline@0.9.1","readme":"ERROR: No README.md file found!","dist":{"shasum":"47644e82c4d1c6778b5b8bf85e10edb5a52a89fa","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.9.1.tgz","integrity":"sha512-hCZiX1QhUSz7Yte2MUBYzFRsgMhGNFNXCqSG9sSfahXdDk1+hncMkSoEo7gd7oYOxH1oczbuuo9FSxgtbSLYQg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDlsbzVBHSF8dMOrpcm6qQTTz4uY3ONqH99oupNVvkI0QIhAPnNwfAT0g4yFJXbOGrI+pgWcOQpuffD3Wt7UfDZsYwS"}]},"_npmVersion":"1.1.59","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.9.2":{"name":"site-manager-baseline","version":"0.9.2","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","jolira-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","_id":"site-manager-baseline@0.9.2","dist":{"shasum":"c23964da1ea0d3f8cf3f2953e659f071866f9de7","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.9.2.tgz","integrity":"sha512-W8wrzLRCvmuverJvcccS8hOdVg6oekrlOzEnng6F3oU4wAvbfmOUoEenfDjl8AlKzzgUaYZV3T+iYXsG2+CXiA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCAowkgnGLrfllYmrB9cU3r2HWN4M3jOb2oU31guFo2iQIgVpJ/cSQJOqx+z39q9puDgbbI54VqPVEwcsuH7pD9F8Y="}]},"_npmVersion":"1.1.59","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"directories":{}},"0.10.0":{"name":"site-manager-baseline","version":"0.10.0","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","jolira-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","_id":"site-manager-baseline@0.10.0","dist":{"shasum":"7ae1da63f323fd4c8b88575426bfeb1661da405c","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.10.0.tgz","integrity":"sha512-SLk30TNkmgTjcRfG4k1aUBMnHMA4WsCAuLO7K4LaLfZvmZ8Xnlv/TKzNpXEGAC8YOuB7gAI6vyC24vuxVJIJNA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDaztj5kv1Reun+X4rswgd/dIHT+MfRtu8t7MgUnIF4cwIhAOQnLbeQhUalz0jqYND+x0Oflw6d5Qum5P3Dpmi9gvjl"}]},"_npmVersion":"1.1.59","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}]},"0.10.1":{"name":"site-manager-baseline","version":"0.10.1","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","jolira-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","_id":"site-manager-baseline@0.10.1","dist":{"shasum":"dec2c280c6ab031252cb8ea2a583b3cdb775ddb5","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.10.1.tgz","integrity":"sha512-QiDa2lBartvY43FXG6Xud2W1VlaqNSSMegNa30xA4Wr2CW52TwamMsVROthBaqucuHg6NnrMek5UsKiP1bNQEA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGwyGRUbSdKAR7HCOZl03dxaAhJgWINp6OVpjsvxR1lUAiEAqz4lU25BMwnlQgCbN6ch4MxoOBlgOUKTZeVa16qNBq8="}]},"_npmVersion":"1.1.59","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}]},"0.10.2":{"name":"site-manager-baseline","version":"0.10.2","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","jolira-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","_id":"site-manager-baseline@0.10.2","dist":{"shasum":"3e6ce76a4f7ff15c3322655a4b1a774b2c05903b","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.10.2.tgz","integrity":"sha512-NSJ0tVAcrMEyPAT1fv4rW15FddaZFGGTUwKAHTF4SCPPgBSU9EsjkjBU6HOGrecrULYqO5C/CaLe+rNU/J28fw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCUrCBC30QF+EVuk3F10mXXZb4DIc0U7icWzWeuSD9PXwIhAMaXgQC+EliWaw8HD08b6XdNe2WVu+xU9b4arh2Cs6xf"}]},"_npmVersion":"1.1.59","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}]},"0.10.3":{"name":"site-manager-baseline","version":"0.10.3","description":"Client-side UI for the Site-Manager applications","keywords":["site","html5","mobile"],"contributors":[{"name":"Joachim Kainz","email":"jfk@jolira.com","url":"http://www.jolira.com"}],"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"},"dependencies":{"socket.io":"*","handlebars":"*","jolira-bootstrap":"*"},"devDependencies":{"site-manager":"*","debug":"*","horaa":"*","vows":"*","jake":"*","uglify-js":"*"},"scripts":{"test":"jake test","prepublish":"npm prune"},"bugs":{"mail":"dev@jolira.com","url":"http://github.com/jolira/site-manager-baseline/issues"},"main":"index","engines":{"node":">= 0.6.0"},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","_id":"site-manager-baseline@0.10.3","dist":{"shasum":"9784a202bbf8b8fa06f5127dcf1b80d27ed2f099","tarball":"https://registry.npmjs.org/site-manager-baseline/-/site-manager-baseline-0.10.3.tgz","integrity":"sha512-KGjmRugZ/lth7BVZLJx2IhYGxCWq9RL62yyPIOWBsK/X5xNXfBTfsxtSVtjgkaa4vYpo01wiuQ7T12Nvwpofvw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC7/qW7dWd5mSwjc0EqWdb80V8aqz2Rv5EO/dt+9466OAIgRMp/NYfskzhS6Hm3y7KXe5+fI/z2u9SY5YuvIF42gIo="}]},"_npmVersion":"1.1.62","_npmUser":{"name":"jfk","email":"jfk@jolira.com"},"maintainers":[{"name":"jfk","email":"jfk@jolira.com"}]}},"readme":"site-manager [<img src=\"https://secure.travis-ci.org/jolira/site-manager.png\" />](http://travis-ci.org/#!/jolira/site-manager)\n========================================\n\nA simple server for developing single-page applictions quickly in a team environment.\n\nThe core of the server are handlebar templates. Here is one handlebar template that comes with the site-manager at\n[``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html).\n\n\nA Very Simple Example\n-----------------------------\n\nCreate a new directory demo appliation in a new directory, such as\n\n```\nmkdir mydemoapp\ncd mydemoapp\n```\n\nCreate a new ``package.json`` declaring site-manager as a dependency.\n\n```\n{\n  \"name\": \"mydemoapp\",\n  \"version\": \"0.0.1\",\n  \"dependencies\": {\n    \"site-manager\": \"*\"\n  },\n  \"main\":\"index\",\n  \"engines\":{\n    \"node\":\">= 0.6.0 < 0.7.0\"\n  }\n}\n```\n\nDeclaring the site-manager is not strictly required, but makes deploying to many systems such as Heroku much\neasier. Instead of declaring the dependency, one case also install the site-manager globally using\n``npm install -g site-manager``.\n\n\nNext, we need a ``index.js`` file:\n\n```\n(function (__dirname, module) {\n    \"use strict\";\n    var path = require(\"path\");\n    module.exports = function (defaults, cb, properties, app) {\n        defaults.useRequireJS = false; // disable the site-manager support for requireJS\n        defaults.hostname = \"mydemoapp.jolira.com\"; // define the name of the site\n        defaults.title = \"My Demo App\"; // The title to be displayed in the titlebar\n        defaults.htmlFiles = [\n            path.join(__dirname, \"content.html\") // add some content\n        ];\n        return cb(undefined, defaults);\n    };\n})(__dirname, module);\n```\n\nNow, all that is remaining is to specify the html-fragment to be displayed when we run the site-manager.\n\n```\n<h1>Hello World!!!</h1>\n```\n\nTo install the dependencies:\n\n```\nnpm install -d\n```\n\nTo run the example:\n\n```\nnode_modules/.bin/site-manager --debug --port=3000 .\n```\n\nTo run the example on Heroku you need the folowing ``Procfile`.\n\n```\nweb: node_modules/.bin/site-manager --debug --port=$PORT --watch-dirs=false .\n```\n\nGo to ``http://localhost:3000/`` to the example running.\n\nConfiguring a Site\n------------------------\n\nAs shown in the example, every site-manager site has configures the site by exporting a function. This function\nlooks like this:\n\n```\n    \"use strict\";\n    module.exports = function (defaults, cb, properties, app) {\n        // configure the defaults object here\n        return cb(undefined, defaults);\n    };\n```\n\nThe default object takes the following parameters:\n\n* ``defaults``: The defaults object to be configured. A detailed description of the properties\n   of this object can be found at\n   [``lib/defaults.json``](https://github.com/jolira/site-manager/blob/master/lib/defaults.js).\n   The [``public/index.html``](https://github.com/jolira/site-manager/blob/master/public/index.html) shows\n   how may of these values are used.\n* ``cb`` the the callback function, which takes two parameters ``cb(err, vals)``. The first parameter\n  should be set to ``undefined``unless there is an error to report. The second parameter should be used\n  to pass the configured default object back to the site-manager.\n* ``properties`` loaded from a ``.config.json`` file in the project directory.\n* ``app`` the [express.js](http://expressjs.com/) object used by the site-manager.\n\nOther Features\n------------------------\n\nKey features of this package are:\n\n* _Teams_: Break the the app into many html fragments to make team development easier.\n* _HTML5Boilerplate_: Our default templates incorporate the latest & greatest boilerplate.\n* _RequireJS_: Teams can (optionally) use [Asynchronous Module Definition](https://github.com/amdjs/amdjs-api/wiki/AMD)\n  to organize their JavaScript.\n* _Auto Reloads_: The site-manager watches the file system for changes and automatically reloads a site when a\n  change is detected.\n* _Less_: Automatically compiles .less files to ``text/css using``.\n* _Properties_: The site-manager loads ``.config.json`` files from the site directory. The site-manager also loads\n  properties from a ``~/.sitemanager.json`` file and passes the data to the different sites it serves.\n* _Manifest_: The site-manager automatically updates [html5\n  manifest](http://www.html5rocks.com/en/tutorials/appcache/beginner/) when changes are detected the require reloading\n  the site.\n* _Developer Support_: The server monitors files and automatically restarts when changes are detected.\n\n### Multi-Site Mode\n\nThe site-manager can run in multi-site mode, which creates virtual hosts for each module. The hostname is defined in\nthe site is used as the server name of the vhost.\n\nIn order to run in multi-site mode, point the site-manager to a directory that contains mutiple sites, such as in\n\n```\nsite-manager examples # use the examples directory from the repo\n```\n\nTo test sites you have to define the correct hostname. In order to do so, you have to add these names to `/etc/hosts`.\nTo define the hostames used by examples from the site-manager github repo, add the following line to `/etc/hosts`\n(assuming you are running the site-manager on your machine):\n\n```\n127.0.0.1\tsimple.jolira.com advanced.jolira.com\n```\n\nOnce this entry has been added, you can access the advanced example as `http://advanced.jolira.com:3000` and the simple\nexample at `http://simple.jolira.com:3000`.\n\n### Single-Site Mode\n\nWhen running in single-site mode, there is no vhosting (as only one site is served). To run the site-manager in\nsingle-site mode, point it to a site directory as in:\n\n```\nsite-manager examples/simple # use the examples directory from the repo\n```\n\nAs there is no virtual hosting, we do not have to define any entry in `/etc/hosts` and can access the example at\n`http://localhost:3000`.\n\n### Enable Debug Output\n\nDebug output is generated when the string `site-manager` is part of the value of the ``NODE_DEBUG`` environment\nvariable.\n\n```\nexport NODE_DEBUG=site-manager\n```\n\nTesting\n-----------------\n\nInstall jake: `npm install -g jake`\n\nNote that Jake is a system-level tool, and wants to be installed globally.\n\nTo execute tests execute: `jake test`\n\nLicense\n-----------------\n\n[MIT License](https://raw.github.com/jolira/site-manager/master/LICENSE.txt)\n\n","maintainers":[{"name":"jfk","email":"jfk@jolira.com"}],"time":{"modified":"2022-06-26T20:21:51.279Z","created":"2012-06-18T17:20:40.021Z","0.0.1":"2012-06-18T17:20:43.090Z","0.1.0":"2012-06-18T17:21:38.325Z","0.1.1":"2012-06-28T00:07:04.680Z","0.1.2":"2012-06-28T01:08:51.600Z","0.1.3":"2012-06-28T06:57:46.436Z","0.1.5":"2012-07-18T23:13:12.016Z","0.2.0":"2012-08-08T14:21:06.494Z","0.3.0":"2012-08-08T23:23:13.730Z","0.8.5":"2012-08-14T22:56:33.026Z","0.8.6":"2012-08-15T03:20:17.342Z","0.8.8":"2012-08-16T18:09:29.727Z","0.8.9":"2012-08-16T23:17:06.360Z","0.8.10":"2012-08-20T20:13:53.845Z","0.8.11":"2012-08-20T20:28:08.159Z","0.8.12":"2012-08-21T23:32:47.782Z","0.8.13":"2012-08-22T00:03:48.057Z","0.8.15":"2012-08-23T16:19:36.890Z","0.9.1":"2012-08-28T20:22:17.088Z","0.9.2":"2012-09-06T05:47:56.118Z","0.10.0":"2012-09-07T04:10:35.453Z","0.10.1":"2012-09-07T06:24:21.793Z","0.10.2":"2012-09-07T22:57:07.547Z","0.10.3":"2012-10-04T01:54:03.257Z"},"repository":{"url":"https://github.com/jolira/site-manager-baseline.git","type":"git"}}