{"_id":"54b2cd6487873d1f00dbebea","project":"54b2c91287873d1f00dbebdb","__v":4,"category":{"_id":"54b2c93f336cfb0b00608c29","__v":3,"project":"54b2c91287873d1f00dbebdb","version":"54b2c93f336cfb0b00608c28","pages":["54b2c940336cfb0b00608c2a","54b2cb7687873d1f00dbebe5","54b2cd6487873d1f00dbebea"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-01-11T19:03:47.125Z","from_sync":false,"order":0,"slug":"introduction","title":"Introduction"},"user":"54a3af95ad78941600ca2e2a","version":{"_id":"54b2c93f336cfb0b00608c28","forked_from":"54b2c91287873d1f00dbebde","project":"54b2c91287873d1f00dbebdb","__v":4,"createdAt":"2015-01-11T19:04:31.031Z","releaseDate":"2015-01-11T19:04:31.031Z","categories":["54b2c93f336cfb0b00608c29","54b2cb87db3c741400eac8c2","54b35d86aad2810b009507d7","54b35d91aad2810b009507d8"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"0.4.0","version":"0.4.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-01-11T19:22:12.913Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"At TES, all of our teams use Bosco to manage their development environments.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Teams\"\n}\n[/block]\nWhenever we start a project we first create a Github team to act as the collation point for all of the repositories that the team will need.  Often repositories are added to more than one team - for example: batteries-not-included, our application template, is added to every team.\n\nAssuming you've got your workspace and team linked, the flow for a developer to get up and running each day looks like this:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"cd workspace\\nbosco morning\\nbosco run -t summary\\nbosco cdn\",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\nLet's go through each of these steps one by one.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"bosco morning\"\n}\n[/block]\nBosco morning is simply a wrapper for a collection of other commands:\n\n* [clone](doc:clone) - clones all of your repositories\n* [pull](doc:pull) - pull any changes \n* [link](doc:link) - link any inter-dependent modules\n* [install](doc:install) - npm install on each\n* [activity](doc:activity) - summary of everything that changed in the last 24 hrs\n\nThis basically ensures that you are 100% up to date and ready to go each morning.  Clearly the name is not a limit on how many times you run it!\n\nYou can use the commands individually throughout the day if you need just any part.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"bosco run -t summary\"\n}\n[/block]\nThis launches all of the projects that are tagged with **summary**, via the [run](doc:run) command.\n\nIn our case, this brings up all of the following services:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/mE60UYmjQzKoAVAf3CkM_Screen%20Shot%202015-01-12%20at%2005.59.39.png\",\n        \"Screen Shot 2015-01-12 at 05.59.39.png\",\n        \"1552\",\n        \"962\",\n        \"#a47f87\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nThis is basically the full set of services that serve the following page:\n\nhttps://www.tes.co.uk/teaching-resource/Sorting-and-Separating-Materials-6001835/\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"bosco cdn\"\n}\n[/block]\nThis starts the local CDN mode of Bosco, that serves up all of the JS and CSS that sit within all of the above services.\n\n[Running a local 'CDN'](doc:running-a-local-cdn) explains how this all works, but in our model it uses [Compoxure](https://github.com/tes/compoxure) and [Bundle Version](https://github.com/tes/bundle-version).\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Work!\"\n}\n[/block]\nYou're now fully up and running, and can start writing code, testing - whatever.","excerpt":"How do teams use Bosco?","slug":"daily-routine","type":"basic","title":"Daily Routine"}

Daily Routine

How do teams use Bosco?

At TES, all of our teams use Bosco to manage their development environments. [block:api-header] { "type": "basic", "title": "Teams" } [/block] Whenever we start a project we first create a Github team to act as the collation point for all of the repositories that the team will need. Often repositories are added to more than one team - for example: batteries-not-included, our application template, is added to every team. Assuming you've got your workspace and team linked, the flow for a developer to get up and running each day looks like this: [block:code] { "codes": [ { "code": "cd workspace\nbosco morning\nbosco run -t summary\nbosco cdn", "language": "shell" } ] } [/block] Let's go through each of these steps one by one. [block:api-header] { "type": "basic", "title": "bosco morning" } [/block] Bosco morning is simply a wrapper for a collection of other commands: * [clone](doc:clone) - clones all of your repositories * [pull](doc:pull) - pull any changes * [link](doc:link) - link any inter-dependent modules * [install](doc:install) - npm install on each * [activity](doc:activity) - summary of everything that changed in the last 24 hrs This basically ensures that you are 100% up to date and ready to go each morning. Clearly the name is not a limit on how many times you run it! You can use the commands individually throughout the day if you need just any part. [block:api-header] { "type": "basic", "title": "bosco run -t summary" } [/block] This launches all of the projects that are tagged with **summary**, via the [run](doc:run) command. In our case, this brings up all of the following services: [block:image] { "images": [ { "image": [ "https://files.readme.io/mE60UYmjQzKoAVAf3CkM_Screen%20Shot%202015-01-12%20at%2005.59.39.png", "Screen Shot 2015-01-12 at 05.59.39.png", "1552", "962", "#a47f87", "" ] } ] } [/block] This is basically the full set of services that serve the following page: https://www.tes.co.uk/teaching-resource/Sorting-and-Separating-Materials-6001835/ [block:api-header] { "type": "basic", "title": "bosco cdn" } [/block] This starts the local CDN mode of Bosco, that serves up all of the JS and CSS that sit within all of the above services. [Running a local 'CDN'](doc:running-a-local-cdn) explains how this all works, but in our model it uses [Compoxure](https://github.com/tes/compoxure) and [Bundle Version](https://github.com/tes/bundle-version). [block:api-header] { "type": "basic", "title": "Work!" } [/block] You're now fully up and running, and can start writing code, testing - whatever.