{"_id":"54fadb625c41173700ecf2a0","version":{"_id":"54fa0050f63cf9210041c3c1","__v":5,"project":"54fa004ff63cf9210041c3be","createdAt":"2015-03-06T19:30:24.258Z","releaseDate":"2015-03-06T19:30:24.258Z","categories":["54fa0050f63cf9210041c3c2","54fa42b3961fea210092068e","54facefd5c41173700ecf296","54fad9d5f63cf9210041c669","54fae9ed5c41173700ecf2ad"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"54fa42b3961fea210092068e","pages":["54fada9b5c41173700ecf29e","54fadb625c41173700ecf2a0","54fae365019b2537006d00bc","5500a5712e8c48170076d163","551a876868da7f0d00f58cbc","5521351e29a3dc0d00fae453","5522b5af85fa041700623976","556d98e442dd610d00a3cfde"],"version":"54fa0050f63cf9210041c3c1","__v":8,"project":"54fa004ff63cf9210041c3be","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-03-07T00:13:39.405Z","from_sync":false,"order":0,"slug":"getting-started","title":"Getting Started"},"project":"54fa004ff63cf9210041c3be","githubsync":"","__v":11,"user":"54fa0018e7a0ba2f00306211","updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-03-07T11:05:06.490Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"Before you can run services on Paz you need to declare them. The Service Directory is the internal service that stores this information, and you can add, edit and remove service in the \"Services\" section of the web UI. Here's how.\n\n* Go to the \"Services\" section of the Paz web UI.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/hjwyOwGaQRu7HIErcfnu_Screen%20Shot%202015-03-11%20at%2001.08.12.png\",\n        \"Screen Shot 2015-03-11 at 01.08.12.png\",\n        \"1264\",\n        \"748\",\n        \"#768aa4\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n* Click \"New service\".\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/tnR6SwooRau5nf3v8zpN_Screen%20Shot%202015-03-11%20at%2001.20.09.png\",\n        \"Screen Shot 2015-03-11 at 01.20.09.png\",\n        \"1264\",\n        \"763\",\n        \"#6b7c9b\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n* Enter the details of your service. The fields are as follows:\n  * *Name*: the service name, used for unique identification and for routing (e.g. naming a service \"api\" means it can be reached from other services by the route \"api\").\n  * *Description*: serves no function other than being descriptive.\n  * *Docker repository*: the repository from which to pull the Docker container for this service. This can include a registry prefix and the repository may be private (which requires you to have configured your CoreOS hosts to have the requisite access to pull the container).\n  * *Number of instances*: the number of instances of this particular service that you'd like the scheduler to launch when it next deploys it.\n  * *Ports*: corresponds to the port mapping arguments of `docker run`. Add as many port mappings as you'd like, or leave it blank to have Paz expose all on random ports.\n  * *Environment*: pass environment variables to the Docker container when it is launched. If you want to specify the URL of one Paz service as an environment variable to another, then use the service's name in here (e.g. \"api\").\n  * *Public Facing*: This determines whether or not Paz will create a subdomain for you with your DNS provider (currently only DNSimple is supported). If you're running in Vagrant this will have no effect.","excerpt":"How to describe your apps to Paz","slug":"deploying-your-first-application-using-paz","type":"basic","title":"Declaring Paz Services"}

Declaring Paz Services

How to describe your apps to Paz

Before you can run services on Paz you need to declare them. The Service Directory is the internal service that stores this information, and you can add, edit and remove service in the "Services" section of the web UI. Here's how. * Go to the "Services" section of the Paz web UI. [block:image] { "images": [ { "image": [ "https://files.readme.io/hjwyOwGaQRu7HIErcfnu_Screen%20Shot%202015-03-11%20at%2001.08.12.png", "Screen Shot 2015-03-11 at 01.08.12.png", "1264", "748", "#768aa4", "" ] } ] } [/block] * Click "New service". [block:image] { "images": [ { "image": [ "https://files.readme.io/tnR6SwooRau5nf3v8zpN_Screen%20Shot%202015-03-11%20at%2001.20.09.png", "Screen Shot 2015-03-11 at 01.20.09.png", "1264", "763", "#6b7c9b", "" ] } ] } [/block] * Enter the details of your service. The fields are as follows: * *Name*: the service name, used for unique identification and for routing (e.g. naming a service "api" means it can be reached from other services by the route "api"). * *Description*: serves no function other than being descriptive. * *Docker repository*: the repository from which to pull the Docker container for this service. This can include a registry prefix and the repository may be private (which requires you to have configured your CoreOS hosts to have the requisite access to pull the container). * *Number of instances*: the number of instances of this particular service that you'd like the scheduler to launch when it next deploys it. * *Ports*: corresponds to the port mapping arguments of `docker run`. Add as many port mappings as you'd like, or leave it blank to have Paz expose all on random ports. * *Environment*: pass environment variables to the Docker container when it is launched. If you want to specify the URL of one Paz service as an environment variable to another, then use the service's name in here (e.g. "api"). * *Public Facing*: This determines whether or not Paz will create a subdomain for you with your DNS provider (currently only DNSimple is supported). If you're running in Vagrant this will have no effect.