{"_id":"ukraine","_rev":"95-f5d06bc3776d6105ec45517bbc2919ce","name":"ukraine","description":"Open Source Node.js PaaS with automatic Proxy and CLI client","dist-tags":{"latest":"0.14.5"},"versions":{"0.5.5":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.5.5","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``config.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. It also uses a custom loader over ``haibu`` injecting a plugin called ``kgb`` that wiretap listens if a new app has been spawned. If it was, it updates the routing table.\n \n There is also a plugin called ``ducktape`` in use that will cleanup any local files before attempting to spawn a new app. Otherwise, we would constantly be spawning an older version of an app.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n","readmeFilename":"README.rst","_id":"ukraine@0.5.5","dist":{"shasum":"350a846a85731bcef3e939378ab4d67a86fc852c","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.5.5.tgz","integrity":"sha512-nmHAI+4/2tqacGKiVP0eSli7HKeoZ7Fe2kj6UeBMdlrQ5GW5l55mg641iBxOEXAITZC8OIU2jcPALbxLd6o5nQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDBnCU1FfN8TX6zyse4iMWpL/AnC8H2nZOaGTulP3r4ZgIgMPNraKo6GgYn+YZ0ILUu1k+H0X910cGavu1huZ1m9II="}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.5.6":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.5.6","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``config.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. It also uses a custom loader over ``haibu`` injecting a plugin called ``kgb`` that wiretap listens if a new app has been spawned. If it was, it updates the routing table.\n \n There is also a plugin called ``ducktape`` in use that will cleanup any local files before attempting to spawn a new app. Otherwise, we would constantly be spawning an older version of an app.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.","readmeFilename":"README.rst","_id":"ukraine@0.5.6","dist":{"shasum":"5237e4d7ee9604c90bc7ec27795e10c8d99d3618","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.5.6.tgz","integrity":"sha512-mNan0Hz7d8Ku72aIzLdTK7+X/UeBIen6REAmW+zwq4tu0U5/Z3a+nWYNEajemx4fYAxluPxi4fhbMUjJPyVqMg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDFOVm1wGlaKgws9PK+tqoM86tIvl9j9lYa30fHZas7ZwIgSaLg8RXFIcLCOoJzG2hslObAJU4EL79pbf0tlNKBC7I="}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.5.7":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.5.7","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``config.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. It also uses a custom loader over ``haibu`` injecting a plugin called ``kgb`` that wiretap listens if a new app has been spawned. If it was, it updates the routing table.\n \n There is also a plugin called ``ducktape`` in use that will cleanup any local files before attempting to spawn a new app. Otherwise, we would constantly be spawning an older version of an app.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.","readmeFilename":"README.rst","_id":"ukraine@0.5.7","dist":{"shasum":"22a78bf5bd330506fd41bbda80c9bec4be65469e","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.5.7.tgz","integrity":"sha512-O3xZyZZWbGYewZL947JnFdHkhq2IrkZvvmjQLy+H9st9CeQH7W9ZWXjUNwTwRu75JpJY9rzyH09SfZzU/Y5TGg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCJLgRthaeCU+nHPT4WInnr4ykPLFah6awK1VxjWLMrDAIhAN2EtoKreSjLmW1lXmFXsrmROkiHRExpGtVieSMxdtXs"}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.7.0":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.7.0","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. It also uses a custom loader over ``haibu`` injecting a plugin called ``kgb`` that wiretap listens if a new app has been spawned. If it was, it updates the routing table.\n \n There is also a plugin called ``ducktape`` in use that will cleanup any local files before attempting to spawn a new app. Otherwise, we would constantly be spawning an older version of an app.\n\n For posting env variables, we add a new router method that maintains a list of apps to env vars passed by the user. Whenever a new app is to be spawned, these vars are injected into its ``package.json`` file.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.","readmeFilename":"README.rst","_id":"ukraine@0.7.0","dist":{"shasum":"61b86c406f05e6fadda2f0124dc8d3035cb7b325","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.7.0.tgz","integrity":"sha512-ESO4U3NoFGmiHU1X2gP9WCnpXI6beQ0kFBbVqHhxE8iv+ETrgB7AhvP4oirfl6ojzeXuf+oPXL7UsKTOoAeGSw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDO9jOwPKY3MHK9+AUtICGkL85+FTnai+pln9J4+q0fBQIhAKaOpa24qlVSG/2GFURB9vVOmsiMmQUIFBRyrxtsIGwg"}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.7.2":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.7.2","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. It also uses a custom loader over ``haibu`` injecting a plugin called ``kgb`` that wiretap listens if a new app has been spawned. If it was, it updates the routing table.\n \n There is also a plugin called ``ducktape`` in use that will cleanup any local files before attempting to spawn a new app. Otherwise, we would constantly be spawning an older version of an app.\n\n For posting env variables, we add a new router method that maintains a list of apps to env vars passed by the user. We save the new environment and then custom restart the app for the changes to take effect.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","readmeFilename":"README.rst","_id":"ukraine@0.7.2","dist":{"shasum":"2efd3a6dfd3569f34c6a6b5ee791f37c56dcdf60","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.7.2.tgz","integrity":"sha512-QYaiFljjvJviGGSIcaTbA5IzgXWCQ3gRZ8XvLaaiu0EQROc5ugcj9kG3oi5QZVDqvz+RBaNNr43fufoHE46u/g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCID4dQBqfsS+cyIWLSePqbyUwly8pUyC1uwQqLShK9rN2AiBWfS6rIJhRtyM1ojAPOwTHB+z5+qbUM5dEnPjYrgFXFQ=="}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.7.3":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.7.3","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. It also uses a custom loader over ``haibu`` injecting a plugin called ``kgb`` that wiretap listens if a new app has been spawned. If it was, it updates the routing table.\n \n There is also a plugin called ``ducktape`` in use that will cleanup any local files before attempting to spawn a new app. Otherwise, we would constantly be spawning an older version of an app.\n\n For posting env variables, we add a new router method that maintains a list of apps to env vars passed by the user. We save the new environment and then custom restart the app for the changes to take effect.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","readmeFilename":"README.rst","_id":"ukraine@0.7.3","dist":{"shasum":"1d3dfee42e143590f1e0a252dea1be0af956d461","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.7.3.tgz","integrity":"sha512-6Wo4WsljOMxxIVRimCUwXZyBUtVGQk5KdEBLpM5cevrOEiFb1zalnfcXgrzWr1BBOLawv+87d0LMLjpt7AklVg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC9r6q+nbOIUifTrp8GTGnUOYuVMl1FT4ik62O3Qmgg7wIgcwafUHfum9UMAxHWFmhkuR+4eI0HFIqf07qlJdW8g5U="}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.8.0":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.8.0","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","readmeFilename":"README.rst","_id":"ukraine@0.8.0","dist":{"shasum":"07674c71ab0380217e5e65c60e1ef1f3b148c496","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.8.0.tgz","integrity":"sha512-1J67gNtoKvfsg2PoCOdn+YKw5A3yDtwhQ+wiwAyfjMNY9PMYOZg+9Cqpu2D9M5V40PXqlmp1ZteWzNq1S1bwUA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCsriaG2QzYSFDHxK766x2AhgmnNo3fL1VUHnTXpP+MEQIhAPl2CPH+lT73lp/50XeuYdk4yIZHHprbnL3uWx2Ck9ng"}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.8.2":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.8.2","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","readmeFilename":"README.rst","_id":"ukraine@0.8.2","dist":{"shasum":"d1d13c4bdef92b7d5bfc8aecb939e6cb30bfd8ea","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.8.2.tgz","integrity":"sha512-CTZInzRIMHi3OIs3QHi9NRqNCYhzMsKmW+Dv3BhlscbqoLhN6uZxXmKuIoR1MPRVzp5KFD8/U+YQkNzyyD+tuQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEwLzuI1+MYfyostDvynRSN7Nt18dfZkib2F6U3mYil3AiEA24mMtT/kgAOr8DgCobg7bqPrm44Rgfuy1aGyQaXSDsY="}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.8.3":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.8.3","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","readmeFilename":"README.rst","_id":"ukraine@0.8.3","dist":{"shasum":"e87de227dcdd4d123ade9321ec9d58d501135641","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.8.3.tgz","integrity":"sha512-KVKG9AC5DK1AaJVfSNK2vCuvOzNCp0YObgi2sYGXYHRFWiBToClepcbDjjow7uscPs2O42b4R2Ic++iVhMOpbg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDcygkCk5bVWH+mHjLPUEvF1Q3pqXfO3uSaa9dgA1ilkgIhAIvnB3++RtkN5hfPEtEQVNJPXtqay2Ew0T6AHtUT7abQ"}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.9.0":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.9.0","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nRemoving the ``auth_token`` key value pair from the config file will make the service exposed to anyone. You may want to change the value...\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","readmeFilename":"README.rst","_id":"ukraine@0.9.0","dist":{"shasum":"4b1bcdff4cd0e4e073cab4bd5c2498ae7c82e226","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.9.0.tgz","integrity":"sha512-plxF95zH6CQBHcip2CJ5BxU0ZE0j5jXdR/k46WBQNnKAILS2SNc8riBpt9IysdeecdEaLsFqENeWqchD+LndmA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCCs8gb8yd5LcETI5jrr+Goe9mSBEAgZANrdMMU/5O2RQIgS8e5RtGdS8Mzj3cTVNTwa6a9he8b+G7o1Mhqruimzzw="}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.9.3":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.9.3","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\"\n }\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nRemoving the ``auth_token`` key value pair from the config file will make the service exposed to anyone. You may want to change the value...\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","readmeFilename":"README.rst","_id":"ukraine@0.9.3","dist":{"shasum":"cd0fdac924b07a551550b891f716503d04a9c8d9","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.9.3.tgz","integrity":"sha512-wa/cm3o/0ei/4TrRWrXgvhrByFWNf6TQvA6pgwxocHXQ5nUVk/rMJ9Y3tIS63xEsQFR07ilymCGXAuoz4mZAYw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIFwwID6sAbYOph+6knYQyMvIxs38mz2GPZQxXnvOPx/2AiBCL6AZkWeMYiX6PLjkX9CAUsrNmftX36AfMcZvVWt7QA=="}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.9.4":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.9.4","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\"\n }\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nRemoving the ``auth_token`` key value pair from the config file will make the service exposed to anyone. You may want to change the value...\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","readmeFilename":"README.rst","_id":"ukraine@0.9.4","dist":{"shasum":"1b4db1c9160d9509c85834d125ece30e471f0e39","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.9.4.tgz","integrity":"sha512-6weXOo3v6zarbC8zHCQlfCDaYA5JqlEsC7C2iqWzFhFq1aM6BUVDQBVymoro9Bpk4GxXKTfBIwJ16Jn3YLCXNQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDabhIA2h7a04EGwRkiLIlHHd3XlXj4kyAJSlT9TAzg8wIhANBsiqbFhXcmCQscsOebbmz9QqA56Vrjp0EFWixuBmso"}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.9.6":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.9.6","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"0.8.5","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\"\n }\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nRemoving the ``auth_token`` key value pair from the config file will make the service exposed to anyone. You may want to change the value...\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","_id":"ukraine@0.9.6","dist":{"shasum":"86bbe43036cf9ae16b99a889c85ad768415da1ce","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.9.6.tgz","integrity":"sha512-w9q3OCFTi6Mfn7RLjQk2XYOozM5OY2pzyUCxrB5wkPEXq5zo/tlHukVUSkjJW3WDPjMayOGGQb+qMA3sgW/C7g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCkwmVZavGqlRdsWZBfH2TQydhzkhNXnL+S0MRkbVziRwIgabdEJq70LxE+rtoLCykbk1J1U/CipDeoJsQVwU1I0E4="}]},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.10.0":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.10.0","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\"\n }\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nRemoving the ``auth_token`` key value pair from the config file will make the service exposed to anyone. You may want to change the value...\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","_id":"ukraine@0.10.0","dist":{"shasum":"be55d2502785e9baf85c590c630c0fdf84198ed7","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.10.0.tgz","integrity":"sha512-8YjfOUZoBi7Cdcxdt0SjcIsytWTwp8JOPczqkwuTstRZJQcLDyEAidsLELa+F92GLjysUpUomX/KRHZD1yHq9Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCEATZwDOtGeiMRm3W8XC6QjyzgJOw9oN7gkeD2zFvjBgIhAMDleCMU9ovnGAXixbAt8KRTgqepfBKzNp0G6seRhvUD"}]},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.10.1":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.10.1","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\"\n }\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file. Edit the ``proxy_host`` property there if you are calling your server another name.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nRemoving the ``auth_token`` key value pair from the config file will make the service exposed to anyone. You may want to change the value...\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","readmeFilename":"README.rst","_id":"ukraine@0.10.1","dist":{"shasum":"f1c90d17322b41ff6ca247ec43e9c1123128e153","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.10.1.tgz","integrity":"sha512-p3b5HzNct4r3Lgn+ZtwXkMSHdKSwzwUHcUEtikPWZAvIoRDM7ybYapQwhedRmoqla7QULhAKuGamqHhtLWYf1w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCuVW6+Owt4a2NVwfCrZz3c3wrZrs/OzXmSauWmM4pL5gIgeNoUU2GHGf6hBJT34o5Sr60IhuShkWRMpLwszo9W7zQ="}]},"_npmVersion":"1.1.66","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.11.0":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.11.0","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","_id":"ukraine@0.11.0","dist":{"shasum":"dd177e2ef1e740938ebc4cc35dda59514514b836","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.11.0.tgz","integrity":"sha512-yYF8uxUlW/P2iV/HmabTq7m2FR1rwmUCHt28ZFPAzA3M+Bx0LbOxhCfZMkcxS/DLcGoaUPCb5nWruvUVVi0gnA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCcjfSjsAeU6qLFmavyJAaTMPOG83YU2dAnZygZIHUqrgIhAJIwJPN9a7xCnhZP8oixiCF29/VxPUNhrhbHzegEY453"}]},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.11.1":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.11.1","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","_id":"ukraine@0.11.1","dist":{"shasum":"0ce652aa751b60ec86b6de2cd17629500a51a2f1","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.11.1.tgz","integrity":"sha512-P3JeYiYhR+ZIdNy9l5dfgSQuFiymlyG0VbUYvIhKUP/wv1HAkojGDBkkCGkI2LIRp+ni/fc/hvGsk9msXCUuIg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEYRYYA2/aj5HZU8Ua0f6W8LJms8HgwLOFnnL38F8ozAAiEAs2+yiV7BjDN94PiOBrv0zwPGvpi2zjlFJqP/3u01vVI="}]},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.11.2":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.11.2","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","_id":"ukraine@0.11.2","dist":{"shasum":"aa665ce7b96fab8f89dfadfdc742ce2b4be55740","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.11.2.tgz","integrity":"sha512-oTm+1uToUXkXLRJwWcFh2uPkEGjesfdvA2BRYRJJ2IbTGStTsS8Hg5wwuzh6++G6yaXmtk3r7jx2nlZnK89oNA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDQKAeZ5hmVbxjz+LVO+7pNl5dFBT5F4NCmktT+h1rHcAIhAO/ldzYoFeoo8ojyGPZ7lb872svv/EbiEdRZKVKmXZ8I"}]},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.11.3":{"name":"ukraine","description":"ukraine glues haibu and node-http-proxy adding a little helper, chernobyl, that deploys into this cloud","version":"0.11.3","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"0.9.7","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11","wrench":"1.4.4"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.","_id":"ukraine@0.11.3","dist":{"shasum":"13ad4a41786643c31bc32c953bbd794d37c28529","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.11.3.tgz","integrity":"sha512-Ei1pYZ51LhrEP2riBp+nemNDj21MO40R8PlX8u+ZEicovVq10gxL+22IsfdOSPpx+sY6IvuFn7R+g+GqcxC0Aw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCQPDSmpusrVnwp3bRiLKCGXPxtaxOJU2z5FnqBUd63zAIhAJHLzIFnfjdr1/+4qYLPAZjJd8Sbe61sCRBE0MSWZ+9y"}]},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.12.0":{"name":"ukraine","description":"Open Source Node.js PaaS with automatic Proxy and CLI client","version":"0.12.0","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"git://github.com/radekstepan/haibu.git#master","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\nOpen Source Node.js PaaS with automatic Proxy and CLI client.\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding a little helper, ``chernobyl``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.\n\nThat is why we use our own version of it since `v0.12.0`\n","readmeFilename":"README.rst","_id":"ukraine@0.12.0","dist":{"shasum":"8a9612bed143ed04688978b7ff6ddf8173228711","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.12.0.tgz","integrity":"sha512-f19xc9px7mNOLfTogmhMCvkYLun0LtEwSR6Qy7GJog7TO09drZTOTYInG4zJv3yLWty0J5vMcHg3Q3y28qTTXA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDZhwFaJBK5YA6Bye3Mligx+XXIqS/NjqpIjSfRV5t5MwIhALAYuIT2qZ85i08g9cdKldBibhub7AVD7eH3EnoRBPqL"}]},"_npmVersion":"1.2.0","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.13.0":{"name":"ukraine","description":"Open Source Node.js PaaS with automatic Proxy and CLI client","version":"0.13.0","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"git://github.com/radekstepan/haibu.git#master","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\nOpen Source Node.js PaaS with automatic Proxy and CLI client.\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding a little helper, ``chernobyl``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\nroot_app\n Setting this value will define which app should we see if we visit the root of this service in the browser. Bear in mind this option will only work if ``proxy_hostname_only`` is set to true. Otherwise you would only see your root app.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.\n\nThat is why we use our own version of it since `v0.12.0`\n","readmeFilename":"README.rst","_id":"ukraine@0.13.0","dist":{"shasum":"bacb269ac6791e6eb972d5d0ecca6e2c87f07409","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.13.0.tgz","integrity":"sha512-bHge05SvI60BIS1wJTU2pP9OzkLPQ82KjyYNxTRrxlOPZSvn/0GEWMpecqDYUdn8tz1yp+gTUWdy7n6UaBBI6g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDF1HmfQ2brmKced6Ki4CeFlSN5E+mF6ZkQYpXqonw+AQIhAKiBbaVHprZCsrptFqlXr/uMPneQs38tfO5PMQY/DR/F"}]},"_npmVersion":"1.2.0","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.14.0":{"name":"ukraine","description":"Open Source Node.js PaaS with automatic Proxy and CLI client","version":"0.14.0","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"git://github.com/radekstepan/haibu.git#master","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\nOpen Source Node.js PaaS with automatic Proxy and CLI client.\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding a little helper, ``chernobyl``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nCustom domains\n~~~~~~~~~~~~~~\n\nWhen the ``proxy_hostname_only`` is set to ``true``, one can define custom domains that the app will respond to by editing the ``server/routes.json`` file adding a ``domains`` list under the app's entry. Example:\n\n.. code-block:: javascript\n\n {\n \"example-app\": {\n \"domains\": [\n \"helios-one.newvegas\"\n ],\n \"host\": \"127.0.0.1\",\n \"port\": 51380\n }\n }\n\nThis means that if we do not match on an app's name domain which is ``/^example-app.newvegas/i``, we will attempt to match on ``/^helios-one.newvegas/i``.\n\nChanges to this file do not require the restarting of the ``ukraine`` instance. The proxy will route on the first match and goes through the domains in a top to bottom fashion. The order of apps is determined by whatever ``for (key in obj) {}`` returns.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.\n\nThat is why we use our own version of it since `v0.12.0`\n","readmeFilename":"README.rst","_id":"ukraine@0.14.0","dist":{"shasum":"d3e42c92f738bc6bfe7e0d1b7f86ae053efecbb9","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.14.0.tgz","integrity":"sha512-w5M2+wnpfR/AGxV9weVM83wAoSIzRfzDTNU5jiAkwyv8fjxgc1zkNHnlM2f9os9c0JFluVThqFbN63MejhHRBw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQC3zOVmvhnTHJ7phat2wwi+UodE754Do6nARGWXMoGiIwIhAK+RPW4E45CoKGTgOr+qZapfY2OfHqrKga6gWvhx7sR0"}]},"_from":".","_npmVersion":"1.2.11","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.14.1":{"name":"ukraine","description":"Open Source Node.js PaaS with automatic Proxy and CLI client","version":"0.14.1","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"git://github.com/radekstepan/haibu.git#master","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\nOpen Source Node.js PaaS with automatic Proxy and CLI client.\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding a little helper, ``chernobyl``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nCustom domains\n~~~~~~~~~~~~~~\n\nWhen the ``proxy_hostname_only`` is set to ``true``, one can define custom domains that the app will respond to by editing the ``server/routes.json`` file adding a ``domains`` list under the app's entry. Example:\n\n.. code-block:: javascript\n\n {\n \"example-app\": {\n \"domains\": [\n \"helios-one.newvegas\"\n ],\n \"host\": \"127.0.0.1\",\n \"port\": 51380\n }\n }\n\nThis means that if we do not match on an app's name domain which is ``/^example-app.newvegas/i``, we will attempt to match on ``/^helios-one.newvegas/i``.\n\nChanges to this file do not require the restarting of the ``ukraine`` instance. The proxy will route on the first match and goes through the domains in a top to bottom fashion. The order of apps is determined by whatever ``for (key in obj) {}`` returns.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.\n\nThat is why we use our own version of it since `v0.12.0`\n","readmeFilename":"README.rst","_id":"ukraine@0.14.1","dist":{"shasum":"7ed33c908d24cc13037dceb3688e99d38a64b198","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.14.1.tgz","integrity":"sha512-uY6B3VtqyZn+B4J1/qYVL1Q4Oo8LvNErnCI/Kxy0bIRS9JCdqQF4fBVZsUSZ+gDWscdX7tst3gcZlBeCuFnh0w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIEGgbK0Q7qVlHQ/nV6wT1VWe7IVCzdkAhUkGxQGQF9zCAiBcK0aXxxYt45tfF2oCiJBSmFl0tGQEehXT3Rz7zjQw0Q=="}]},"_from":".","_npmVersion":"1.2.11","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.14.2":{"name":"ukraine","description":"Open Source Node.js PaaS with automatic Proxy and CLI client","version":"0.14.2","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"git://github.com/radekstepan/haibu.git#master","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\nOpen Source Node.js PaaS with automatic Proxy and CLI client.\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding a little helper, ``chernobyl``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nCustom domains\n~~~~~~~~~~~~~~\n\nWhen the ``proxy_hostname_only`` is set to ``true``, one can define custom domains that the app will respond to by editing the ``server/routes.json`` file adding a ``domains`` list under the app's entry. Example:\n\n.. code-block:: javascript\n\n {\n \"example-app\": {\n \"domains\": [\n \"helios-one.newvegas\"\n ],\n \"host\": \"127.0.0.1\",\n \"port\": 51380\n }\n }\n\nThis means that if we do not match on an app's name domain which is ``/^example-app.newvegas/i``, we will attempt to match on ``/^helios-one.newvegas/i``.\n\nChanges to this file do not require the restarting of the ``ukraine`` instance. The proxy will route on the first match and goes through the domains in a top to bottom fashion. The order of apps is determined by whatever ``for (key in obj) {}`` returns.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.\n\nThat is why we use our own version of it since `v0.12.0`\n","readmeFilename":"README.rst","_id":"ukraine@0.14.2","dist":{"shasum":"47b91217f13eefa34a471e27e219b8f328fd7ae4","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.14.2.tgz","integrity":"sha512-BUXekRZJiI4ZjyzlkZAfW5mVDrHOVHteE4TY+PuOfaTSyqMZuDlgFNu5kqvN9PEVuF/G2oUwtqVEHleXvGVmdw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDfWqyviHhx2NxsDar+ab7EDR7DJNZCHfmS/4izpwj+dQIhAJ1XjzTn76oYXd8iF5rNoJX0yC3lDxbndig6px/B84cs"}]},"_from":".","_npmVersion":"1.2.11","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.14.3":{"name":"ukraine","description":"Open Source Node.js PaaS with automatic Proxy and CLI client","version":"0.14.3","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"git://github.com/radekstepan/haibu.git#master","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\nOpen Source Node.js PaaS with automatic Proxy and CLI client.\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding a little helper, ``chernobyl``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nCustom domains\n~~~~~~~~~~~~~~\n\nWhen the ``proxy_hostname_only`` is set to ``true``, one can define custom domains that the app will respond to by editing the ``server/routes.json`` file adding a ``domains`` list under the app's entry. Example:\n\n.. code-block:: javascript\n\n {\n \"example-app\": {\n \"domains\": [\n \"helios-one.newvegas\"\n ],\n \"host\": \"127.0.0.1\",\n \"port\": 51380\n }\n }\n\nThis means that if we do not match on an app's name domain which is ``/^example-app.newvegas/i``, we will attempt to match on ``/^helios-one.newvegas/i``.\n\nChanges to this file do not require the restarting of the ``ukraine`` instance. The proxy will route on the first match and goes through the domains in a top to bottom fashion. The order of apps is determined by whatever ``for (key in obj) {}`` returns.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.\n\nThat is why we use our own version of it since `v0.12.0`\n","readmeFilename":"README.rst","_id":"ukraine@0.14.3","dist":{"shasum":"17637feb4376d4ccb1b39185453e10b5ea3cc489","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.14.3.tgz","integrity":"sha512-n4DquczQm9gtW2P3oJ6hSU1GmwCpFC1DLGMLSEVLyJY9W80DfH264DuozX/WW3J/bh3dns2fqSR78hlzRrxmBA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDSPoMWBjiXvhLVdsIq2GTQoI80+Ou8UFg4wtCPGZZZTAiEAt8sfAH6yshSCWbRuQJ+eFu9HlvSqKE8Yuo5J8Ei+J7Q="}]},"_from":".","_npmVersion":"1.2.11","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.14.4":{"name":"ukraine","description":"Open Source Node.js PaaS with automatic Proxy and CLI client","version":"0.14.4","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"git://github.com/radekstepan/haibu.git#master","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\nOpen Source Node.js PaaS with automatic proxy and cli client.\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding a little helper, ``chernobyl``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nCustom domains\n~~~~~~~~~~~~~~\n\nWhen the ``proxy_hostname_only`` is set to ``true``, one can define custom domains that the app will respond to by editing the ``server/routes.json`` file adding a ``domains`` list under the app's entry. Example:\n\n.. code-block:: javascript\n\n {\n \"example-app\": {\n \"domains\": [\n \"helios-one.newvegas\"\n ],\n \"host\": \"127.0.0.1\",\n \"port\": 51380\n }\n }\n\nThis means that if we do not match on an app's name domain which is ``/^example-app.newvegas/i``, we will attempt to match on ``/^helios-one.newvegas/i``.\n\nChanges to this file do not require the restarting of the ``ukraine`` instance. The proxy will route on the first match and goes through the domains in a top to bottom fashion. The order of apps is determined by whatever ``for (key in obj) {}`` returns.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nHaibu is a poorly written piece of software, be aware of these facts:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.\n\nThat is why we use our own version of it since `v0.12.0`\n","readmeFilename":"README.rst","_id":"ukraine@0.14.4","dist":{"shasum":"fc14db8c0e77c832eb9a3518c163eb870473401a","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.14.4.tgz","integrity":"sha512-6rEa5mFs9pF21s1RZyyinJ9bIjj4roKKkO5n5RjUmbkN0d1XxXZMN9dR/wCybksGVLV9bj+IGs/duyekKY0AeA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCnmmGVZSRMgI09r9HZ0ZDbdSnq7CP2NkKybi18K0tPXQIgc3HA5mFjpJ8M4FFZg5TDCxTqKfNa+uCsfmKntV/PsSU="}]},"_from":".","_npmVersion":"1.3.2","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"directories":{}},"0.14.5":{"name":"ukraine","description":"Open Source Node.js PaaS with automatic Proxy and CLI client","version":"0.14.5","dependencies":{"coffee-script":"1.4.0","winston":"0.6.2","colors":"0.6.0-1","flatiron":"0.3.0","haibu":"git://github.com/radekstepan/haibu.git#master","http-proxy":"git://github.com/radekstepan/node-http-proxy.git#master","tar":"git://github.com/radekstepan/node-tar.git#master","fstream":"0.1.19","request":"2.12.0","q":"0.8.11"},"bin":{"ukraine":"./bin/ukraine","chernobyl":"./bin/chernobyl"},"readme":"ukraine\n=========\n\nOpen Source Node.js PaaS with automatic proxy and cli client.\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding a little helper, ``chernobyl``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nCreate a ``config.json`` file if not present already in the lib's root:\n\n.. code-block:: json\n\n {\n \"haibu_port\": 9002,\n \"proxy_port\": 80,\n \"proxy_host\": \"127.0.0.1\",\n \"auth_token\": \"abc\",\n \"proxy_hostname_only\": false\n }\n\nhaibu_port\n On which port to start the Haibu service.\nproxy_port\n Where will all requests go? If set to ``80``, you will be able to access your apps without providing a port number.\nproxy_host\n What is the host used in the proxy routing table. This is the 'domain' you will be using to access the running apps.\nauth_token\n A token that a client will need to use to access the ukraine service. Leaving this property out will not require you to pass a token and is useful for debugging.\nproxy_hostname_only\n If set to ``true`` your apps will be routed from ``.:`` instead of ``://``. Useful also in a case when you have links in your app that are root relative.\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\n.. note::\n In order to run the server in the background, I recommend you install `forever.js `_ and start the service as follows:\n\n .. code-block:: bash\n\n $ sudo npm install forever -g\n $ sudo forever start /usr/local/lib/node_modules/ukraine/bin/ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``package.json`` file. You can also use the ``chernobyl`` app itself to pass them if you do not want to expose them in a public ``package.json`` file.\n\nCustom domains\n~~~~~~~~~~~~~~\n\nWhen the ``proxy_hostname_only`` is set to ``true``, one can define custom domains that the app will respond to by editing the ``server/routes.json`` file adding a ``domains`` list under the app's entry. Example:\n\n.. code-block:: javascript\n\n {\n \"example-app\": {\n \"domains\": [\n \"helios-one.newvegas\"\n ],\n \"host\": \"127.0.0.1\",\n \"port\": 51380\n }\n }\n\nThis means that if we do not match on an app's name domain which is ``/^example-app.newvegas/i``, we will attempt to match on ``/^helios-one.newvegas/i``.\n\nChanges to this file do not require the restarting of the ``ukraine`` instance. The proxy will route on the first match and goes through the domains in a top to bottom fashion. The order of apps is determined by whatever ``for (key in obj) {}`` returns.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. All (useful) routes to ``haibu`` have been overwritten using promises.\n \n New method for posting env vars has been added.\n\n Token authentication per ukraine instance has been added too.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. check if we need to auth to deploy an app\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n\nTroubleshooting\n---------------\n\nBe aware of these facts re ukraine/haibu:\n\n#. If you intend to use the API haibu exposes, be sure to send correct parameters in the right format, otherwise you will shut down the app.\n#. Your ``package.json`` start script can only include a file name, not a bash command! Haibu checks that whatever you put in there is an existing file. Even more annoyingly, the file needs to be a js file that node can call.\n#. Sometimes zlib complains when streaming a package, the code here attempts to keep packing and streaming apps to deploy if it gets these errors.\n#. Uploading a new version of the app would not necessarily invalidate the old version, thus we brutforce remove the previous apps.\n#. When an app is deployed, it might still take a second or two for it to actually show over the proxy server.\n#. Although it should be allowed, haibu only allows to kill an app by its name, not name and username so we all deploy apps into a ``chernobyl`` namespace and if you want to deploy the same app again on a different port, you need to change its ``name`` in ``config.json``.\n#. Restarting the app does not work as one would expect getting the latest env variables, stopping does not either expecting an ``application`` object instead of the ``name`` it is passed from the service. When setting new environment variable, then, we take a custom approach of stopping a running instance, getting the latest hash of its package and starting it again with these settings.\n\nThat is why we use our own version of it since `v0.12.0`\n","readmeFilename":"README.rst","_id":"ukraine@0.14.5","dist":{"shasum":"1a79dae2bcf8012606c6f320fccd062812eee486","tarball":"https://registry.npmjs.org/ukraine/-/ukraine-0.14.5.tgz","integrity":"sha512-wPkL2iesw9yyndFRO/AlMllJ3dZSqax9tLZgHh+aBq6FaU9z6mmSNGYwdGCtHBdOgJuBOk8gb6A9Osmrtzgw/g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIC6+XPVDeQV3XmzRA9Wpdq4AdJ2v//Aah4IpiNTE7ep3AiEA3mysHI8eNqlhh52i8JUQ+9Md3MgkeLIA6SDe9BH/NJg="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"radekstepan","email":"dev@radekstepan.com"},"maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}]}},"readme":"ukraine\n=========\n\n``ukraine`` glues ``haibu`` and ``node-http-proxy`` adding two little helpers, ``chernobyl`` and ``ducktape``, that deploys into this cloud. It is probably as stable as you think it is.\n\n.. image:: https://raw.github.com/radekstepan/ukraine/master/example.png\n\nQuick start\n-----------\n\nMake sure you have ``node >= 0.8.0`` `installed `_, 0.8.15 is recommended as current stable.\n\nInstall the package globally:\n\n.. code-block:: bash\n\n $ sudo npm install ukraine -g\n\nAs a server\n~~~~~~~~~~~\n\nStart it up:\n\n.. code-block:: bash\n\n $ sudo ukraine\n\nAs a client\n~~~~~~~~~~~\n\nMove to a directory with the app to deploy. Deploy pointing to cloud instance:\n\n.. code-block:: bash\n\n $ chernobyl deploy \n\nConfig\n-----------\n\nTo set the ports the proxy and haibu are supposed to be listening on, edit the ``config.json`` file.\n\nFor setting environment variables exposed through ``process.env``, set the key value pair ``env`` in your app's ``config.json`` file.\n\nArchitecture\n------------\n\nukraine\n Spawns a ``node-http-proxy`` server that dynamically watches for changes in a routing table. It also uses a custom loader over ``haibu`` injecting a plugin called ``kgb`` that wiretap listens if a new app has been spawned. If it was, it updates the routing table.\n \n There is also a plugin called ``ducktape`` in use that will cleanup any local files before attempting to spawn a new app. Otherwise, we would constantly be spawning an older version of an app.\n\nchernobyl\n #. checks that your app's `package.json` file is in order\n #. checks that ``ukraine`` instance is up\n #. checks and stops an existing app if need be\n #. packs the new app and sends it to the cloud to deploy\n","maintainers":[{"name":"radekstepan","email":"dev@radekstepan.com"}],"time":{"modified":"2022-06-28T03:37:59.469Z","created":"2012-12-05T15:53:39.368Z","0.5.5":"2012-12-05T15:53:41.335Z","0.5.6":"2012-12-05T17:12:13.729Z","0.5.7":"2012-12-05T17:23:52.624Z","0.7.0":"2012-12-06T00:39:05.447Z","0.7.2":"2012-12-07T23:00:30.274Z","0.7.3":"2012-12-08T00:38:48.107Z","0.8.0":"2012-12-08T14:10:09.147Z","0.8.2":"2012-12-08T14:43:53.286Z","0.8.3":"2012-12-08T15:03:18.429Z","0.9.0":"2012-12-08T18:16:08.437Z","0.9.3":"2012-12-09T01:08:54.600Z","0.9.4":"2012-12-09T01:46:16.755Z","0.9.6":"2012-12-13T12:24:34.623Z","0.10.0":"2012-12-13T19:03:59.208Z","0.10.1":"2012-12-13T22:40:57.742Z","0.11.0":"2012-12-14T13:04:22.582Z","0.11.1":"2012-12-14T13:27:51.704Z","0.11.2":"2012-12-14T13:36:03.925Z","0.11.3":"2012-12-14T13:42:39.920Z","0.12.0":"2013-01-19T11:04:15.499Z","0.13.0":"2013-02-18T21:24:44.313Z","0.14.0":"2013-02-28T12:26:37.859Z","0.14.1":"2013-03-06T18:29:15.858Z","0.14.2":"2013-03-12T13:48:03.917Z","0.14.3":"2013-03-12T13:55:01.574Z","0.14.4":"2013-09-23T11:25:32.732Z","0.14.5":"2013-09-25T10:31:22.366Z"},"users":{}}