{"_id":"portland","_rev":"53-c392a13d0e2ec3e5884099eacd735fd4","name":"portland","description":"100% locally grown ports","dist-tags":{"latest":"0.0.10"},"versions":{"0.0.1":{"name":"portland","description":"100% locally grown ports","version":"0.0.1","author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"},"dependencies":{"semver":"1.1.0","cui":"0.0.4"},"bin":{"portland":"bin/portland.js"},"readme":"# portland\n100% locally grown ports","readmeFilename":"README.md","_id":"portland@0.0.1","dist":{"shasum":"4584e3689294d8968165e17174e222d811c3071e","tarball":"https://registry.npmjs.org/portland/-/portland-0.0.1.tgz","integrity":"sha512-QAaQ5paEh2UD5nlW5iRjHIspOdwsFBSv3LQ/SmUOQmKPFj9G8DbPoZLdRxmtXCI1oIT9QQ2Caq41D3/d1zIUZw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC+4FW3pXPSRKDIeCLyyaY3RLvJ2B3K0Kc3I073EwyFZAIgZ/BD3K5KoT9DuEwxN1prKCm8Wmz99s5U0xtuHatN2sg="}]},"_npmVersion":"1.1.65","_npmUser":{"name":"jessetane","email":"jesse.tane@gmail.com"},"maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}],"directories":{}},"0.0.2":{"name":"portland","description":"100% locally grown ports","version":"0.0.2","author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"},"dependencies":{"semver":"1.1.0","cui":"0.0.4"},"bin":{"portland":"bin/portland.js"},"readme":"# portland\n100% locally grown ports","readmeFilename":"README.md","_id":"portland@0.0.2","dist":{"shasum":"88003ed1dbba6e71e46ba81ba856e10d1bf71935","tarball":"https://registry.npmjs.org/portland/-/portland-0.0.2.tgz","integrity":"sha512-rvP6nWPsXdlyLB1V5FvRuqgrhowHc6spvMqIaoP2cznmMl3bN7HziwiDZzLYQESEo0stTWAo7O7nh7vNN9f6pA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEer5+OKt5ssCAKeB7LltlA49DfcN2R1bSA2utKAizTYAiEAxz9+zsgjUSgOTXe4K56r6nBPJiN8yuR506Fsty51iwU="}]},"_npmVersion":"1.1.65","_npmUser":{"name":"jessetane","email":"jesse.tane@gmail.com"},"maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}],"directories":{}},"0.0.3":{"name":"portland","description":"100% locally grown ports","version":"0.0.3","author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"},"dependencies":{"semver":"1.1.0","cui":"0.0.4"},"bin":{"portland":"bin/portland.js"},"readme":"```\neeeee eeeee eeeee eeeee e     eeeee eeeee eeeee \n8   8 8  88 8   8   8   8     8   8 8   8 8   8 \n8eee8 8   8 8eee8e  8e  8e    8eee8 8e  8 8e  8 \n88    8   8 88   8  88  88    88  8 88  8 88  8 \n88    8eee8 88   8  88  88eee 88  8 88  8 88ee8\n```\n100% locally grown ports.\n\n## Why\nIt can be a pain to manually assign port numbers to network services. They might deploy to multifarious environments or run concurrently at multiple versions in a single environment, making configuration tedious. Portland provides a registry to help automate this process.\n\n## How\nPortland has two parts: a client and a server. The server contains the registry itself, so each host should run exactly one. Local services can then use the portland client (via command line tool or embeddable library) to register themselves, or lookup other services they depend on.\n\n## Install\n```npm install portland -g```\n\n## Usage\nThis is mostly just an experiment. I'll update this if / when I actually end up using it...\n\n## Inspiration\n[seaport](https://github.com/substack/seaport.git)\n\n## License\nMIT","readmeFilename":"README.md","_id":"portland@0.0.3","dist":{"shasum":"e58ee895eee7c5bd216271a36ef1889dad5e0e30","tarball":"https://registry.npmjs.org/portland/-/portland-0.0.3.tgz","integrity":"sha512-QAQPgzEZZfssay/eIrXYyDXsNhfCVeFcG3Fm8zDZlVsnY74jtifxn/nV9WBm2I1N4XadflmTwtSIpRD4aa3NSw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQC+yE/a4mS3LqAhT3GLO4Ov7HMJ4OGfVDiTHHGRz6vViwIgEyie+cUi7z0/bcXmMfXV10TIBSyrach3iI3he2GMw6o="}]},"_npmVersion":"1.1.65","_npmUser":{"name":"jessetane","email":"jesse.tane@gmail.com"},"maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}],"directories":{}},"0.0.4":{"name":"portland","description":"100% locally grown ports","version":"0.0.4","author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"},"dependencies":{"mkdirp":"0.3.3","semver":"1.1.0","cui":"0.0.4"},"bin":{"portland":"bin/portland.js"},"readme":"```\neeeee eeeee eeeee eeeee e     eeeee eeeee eeeee \n8   8 8  88 8   8   8   8     8   8 8   8 8   8 \n8eee8 8   8 8eee8e  8e  8e    8eee8 8e  8 8e  8 \n88    8   8 88   8  88  88    88  8 88  8 88  8 \n88    8eee8 88   8  88  88eee 88  8 88  8 88ee8\n```\n100% locally grown ports.\n\n## Why\nIt can be a pain to manually assign port numbers to network services. They might deploy to multifarious environments or run concurrently at multiple versions in a single environment, making configuration tedious. Portland provides a registry to help automate this process.\n\n## How\nPortland has two parts: a client and a server. The server contains the registry itself, so each host should run exactly one. Local services can then use the portland client (via command line tool or embeddable library) to register themselves, or lookup other services they depend on.\n\n## Install\n```npm install portland -g```\n\n## Usage\nNot stable... an experiment for now.\n\n## Inspiration\n[seaport](https://github.com/substack/seaport.git)\n\n## License\nBEER","readmeFilename":"README.md","_id":"portland@0.0.4","dist":{"shasum":"dca04896d6064014d64165e748ed96738505f720","tarball":"https://registry.npmjs.org/portland/-/portland-0.0.4.tgz","integrity":"sha512-qU1oieStoJlr9U2wITwEvrap7EMTjZptbuySNDjiLvLdJApskrkRAjJTJnD9vjTXIakURz/Y5wzDo3O+gozuQA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIBCFvTL87AL/Rq9g08sgpVIK47L34o67rbTPF5aV/bJlAiB94Z3pIOym4QWZe9g/N467sTDHAQVZttkAbBogSKdZ7A=="}]},"_npmVersion":"1.1.65","_npmUser":{"name":"jessetane","email":"jesse.tane@gmail.com"},"maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}],"directories":{}},"0.0.5":{"name":"portland","description":"100% locally grown ports","version":"0.0.5","author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"},"dependencies":{"mkdirp":"0.3.3","semver":"1.1.0","cui":"0.0.4"},"bin":{"portland":"bin/portland.js"},"readme":"```\neeeee eeeee eeeee eeeee e     eeeee eeeee eeeee \n8   8 8  88 8   8   8   8     8   8 8   8 8   8 \n8eee8 8   8 8eee8e  8e  8e    8eee8 8e  8 8e  8 \n88    8   8 88   8  88  88    88  8 88  8 88  8 \n88    8eee8 88   8  88  88eee 88  8 88  8 88ee8\n```\n100% locally grown ports.\n\n## Why\nIt can be a pain to manually assign port numbers to network services. They might deploy to multifarious environments or run concurrently at multiple versions in a single environment, making configuration tedious. Portland provides a registry to help automate this process.\n\n## How\nPortland has two parts: a client and a server. The server contains the registry itself, so each host should run exactly one. Local services can then use the portland client (via command line tool or embeddable library) to register themselves, or lookup other services they depend on.\n\n## Install\n```npm install portland -g```\n\n## Usage\nNot stable... an experiment for now.\n\n## Inspiration\n[seaport](https://github.com/substack/seaport.git)\n\n## License\nBEER","readmeFilename":"README.md","_id":"portland@0.0.5","dist":{"shasum":"b32958c0336755bbfae579d3c78ed0bd39edf36c","tarball":"https://registry.npmjs.org/portland/-/portland-0.0.5.tgz","integrity":"sha512-EZhIMb90Fa+E8gZ2eqtR2FRxkrb5fhu00DK5jPvJ0anujlDMTgE1ZoacQdiYXR57ZVDxCUKZwaG5So7dtLK9fw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIAgxPM/+UaWdxCCteHbDKr7O3QDsdhzbO8uCDfCM3VHwAiEA1rEkiA4C0tYDV/e/UnB9Ad9z7/kHCt/NeHiyYxcfbhs="}]},"_npmVersion":"1.1.65","_npmUser":{"name":"jessetane","email":"jesse.tane@gmail.com"},"maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}],"directories":{}},"0.0.7":{"name":"portland","description":"100% locally grown ports","version":"0.0.7","author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"},"dependencies":{"semver":"1.1.0","cui":"0.0.6"},"bin":{"portland":"bin/portland.js"},"readme":"```\neeeee eeeee eeeee eeeee e     eeeee eeeee eeeee \n8   8 8  88 8   8   8   8     8   8 8   8 8   8 \n8eee8 8   8 8eee8e  8e  8e    8eee8 8e  8 8e  8 \n88    8   8 88   8  88  88    88  8 88  8 88  8 \n88    8eee8 88   8  88  88eee 88  8 88  8 88ee8\n```\n100% locally grown ports.\n\n## Why\nIt can be a pain to manually assign port numbers to network services. They might deploy to multifarious environments or run concurrently at multiple versions in a single environment, making configuration tedious. Portland provides a registry to help automate this process.\n\n## How\nPortland has two parts: a client and a server. The server contains the registry itself, so each host should run exactly one. Local services can then use the portland client (via command line tool or embeddable library) to register themselves, or lookup other services they depend on.\n\n## Install\n```npm install portland -g```\n\n## Usage\nNot stable... an experiment for now.\n\n## Inspiration\n[seaport](https://github.com/substack/seaport.git)\n\n## License\nMIT","readmeFilename":"README.md","_id":"portland@0.0.7","dist":{"shasum":"e6e99a96bdcf87d0513a845fc9931e0ff4857d19","tarball":"https://registry.npmjs.org/portland/-/portland-0.0.7.tgz","integrity":"sha512-ZzYKnrdPXPrAzZWy5GjB2grX3f8y5IkcG98AFV76iP2BN9Cw7li9DqSjxBQKaI2Mda8GBvLMWHVl6Oa+XCluoA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCvOsUrFe52JUH8EumsyDFkkVrqbBEXUnl0VuLbh6/sIQIhAL/11As6ynUIrN0rXvPUp/J/DMf23yBWauQ2z78a19N2"}]},"_npmVersion":"1.1.65","_npmUser":{"name":"jessetane","email":"jesse.tane@gmail.com"},"maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}],"directories":{}},"0.0.8":{"name":"portland","description":"100% locally grown ports","version":"0.0.8","author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"},"dependencies":{"semver":"1.1.0","cui":"0.0.6"},"bin":{"portland":"bin/portland.js"},"readme":"```\neeeee eeeee eeeee eeeee e     eeeee eeeee eeeee \n8   8 8  88 8   8   8   8     8   8 8   8 8   8 \n8eee8 8   8 8eee8e  8e  8e    8eee8 8e  8 8e  8 \n88    8   8 88   8  88  88    88  8 88  8 88  8 \n88    8eee8 88   8  88  88eee 88  8 88  8 88ee8\n```\n100% locally grown ports.\n\n## Why\nIt can be a pain to manually assign port numbers to network services. They might deploy to multifarious environments or run concurrently at multiple versions in a single environment, making configuration tedious. Portland provides a registry to help automate this process.\n\n## How\nPortland has two parts: a client and a server. The server contains the registry itself, so each host should run exactly one. Local services can then use the portland client (via command line tool or embeddable library) to register themselves, or lookup other services they depend on.\n\n## Install\n```npm install portland -g```\n\n## Usage\nNot stable... an experiment for now.\n\n## Inspiration\n[seaport](https://github.com/substack/seaport.git)\n\n## License\nMIT","readmeFilename":"README.md","_id":"portland@0.0.8","dist":{"shasum":"ac975eb3db264cdeeaad77318f3d2b755dbe1fe2","tarball":"https://registry.npmjs.org/portland/-/portland-0.0.8.tgz","integrity":"sha512-nWbYXAr4GOpg2OwXDqal2NHAmEED8HYlWNsdxlENrLhwbVYzP3EUHitD2uwkcWdECRKaCQZm0apTMypZugm28Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIG1ZF3Fx3NrXaqC7bGUMsxzsW0jZY5Q4OADpubiSQBapAiAu1sDxtZ/UMLfAGh4K7zpsetjS9k3M3WrNWVV8ENfBAg=="}]},"_npmVersion":"1.1.65","_npmUser":{"name":"jessetane","email":"jesse.tane@gmail.com"},"maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}],"directories":{}},"0.0.9":{"name":"portland","description":"100% locally grown ports","version":"0.0.9","author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"},"dependencies":{"semver":"1.1.0","cui":"0.0.6"},"bin":{"portland":"bin/portland.js"},"readme":"```\neeeee eeeee eeeee eeeee e     eeeee eeeee eeeee \n8   8 8  88 8   8   8   8     8   8 8   8 8   8 \n8eee8 8   8 8eee8e  8e  8e    8eee8 8e  8 8e  8 \n88    8   8 88   8  88  88    88  8 88  8 88  8 \n88    8eee8 88   8  88  88eee 88  8 88  8 88ee8\n```\n100% locally grown ports.\n\n## Why\nIt can be a pain to manually assign port numbers to network services. They might deploy to multifarious environments or run concurrently at multiple versions in a single environment, making configuration tedious. Portland provides a registry to help automate this process.\n\n## How\nPortland has two parts: a client and a server. The server contains the registry itself, so each host should run exactly one. Local services can then use the portland client (via command line tool or embeddable library) to register themselves, or lookup other services they depend on.\n\n## Install\n```npm install portland -g```\n\n## Usage\nNot stable... an experiment for now.\n\n## Inspiration\n[seaport](https://github.com/substack/seaport.git)\n\n## License\nMIT","readmeFilename":"README.md","_id":"portland@0.0.9","dist":{"shasum":"ceee314b0cbb70071540c3568363f987ff77d19c","tarball":"https://registry.npmjs.org/portland/-/portland-0.0.9.tgz","integrity":"sha512-Io7tnXqs0vCitkiQBRGm0FqUnZGyktGq4v2wSczhudHbR61vHNFnN6j0Vt1vYjp8amUo/CdEKtyAVS1PqL3KQg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCfpvs3BKPTVgvEKy2AK5C/J5nBtMzQJGSYSLUrsHp4TwIgLYZQmuvMaxyHbA6hcb/TsuIRvPmb8eQbw+zoRdBeVtY="}]},"_npmVersion":"1.1.65","_npmUser":{"name":"jessetane","email":"jesse.tane@gmail.com"},"maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}],"directories":{}},"0.0.10":{"name":"portland","description":"100% locally grown ports","version":"0.0.10","author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"},"dependencies":{"semver":"1.1.0","cui":"0.0.10"},"bin":{"portland":"bin/portland.js","pdx":"bin/portland.js"},"readme":"```\neeeee eeeee eeeee eeeee e     eeeee eeeee eeeee \n8   8 8  88 8   8   8   8     8   8 8   8 8   8 \n8eee8 8   8 8eee8e  8e  8e    8eee8 8e  8 8e  8 \n88    8   8 88   8  88  88    88  8 88  8 88  8 \n88    8eee8 88   8  88  88eee 88  8 88  8 88ee8\n```\n100% locally grown ports.\n\n## Why\nIt can be a pain to manually assign port numbers to network services. Portland provides a registry to help automate this process.\n\n## How\nPortland has two parts: a client and a server. The server contains the registry itself, so each host should run exactly one. Local services can then use the portland client (via command line tool or embeddable library) to register themselves, or lookup other services they depend on.\n\n## Install\n`npm install portland -g`\n\n## Usage\nNot stable... an experiment for now.\n\n## Inspiration\n[seaport](https://github.com/substack/seaport.git)\n\n## License\nMIT","readmeFilename":"README.md","_id":"portland@0.0.10","dist":{"shasum":"f2f9f905cceca9f29a7ac298089bd0aaa652860b","tarball":"https://registry.npmjs.org/portland/-/portland-0.0.10.tgz","integrity":"sha512-VVvaYUedWzF6iAZTbAySUOzP5bclUdNJmBj3a7iVc4+YxWrbsnPPu32gt5rd+jZhI5uxOw90RvgOaIjWHI+mPw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGGISYUwtk+i/NubO+l6tiN67c/M4/RL7zdEqxnCbAAGAiEAwMeXeni0p25uL82XRDzmSHZhhFXJpx2I4jaCmV9QUAI="}]},"_npmVersion":"1.2.0","_npmUser":{"name":"jessetane","email":"jesse.tane@gmail.com"},"maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}]}},"readme":"# portland\n100% locally grown ports","maintainers":[{"name":"jessetane","email":"jesse.tane@gmail.com"}],"time":{"modified":"2022-06-24T08:56:28.200Z","created":"2012-11-18T00:48:46.800Z","0.0.1":"2012-11-18T00:48:47.590Z","0.0.2":"2012-11-18T21:12:06.307Z","0.0.3":"2012-11-19T21:58:25.437Z","0.0.4":"2012-11-28T15:59:23.749Z","0.0.5":"2012-11-28T17:18:43.420Z","0.0.7":"2012-12-01T02:16:12.179Z","0.0.8":"2012-12-05T01:47:39.018Z","0.0.9":"2012-12-07T17:53:32.518Z","0.0.10":"2013-01-24T08:36:32.775Z","0.0.11":"2013-01-24T07:38:39.877Z"},"author":{"name":"Jesse Tane","email":"jesse.tane@gmail.com"}}