{"id":"54b2c91287873d1f00dbebdb","name":"bosco","subdomain":"bosco","versions":[{"_id":"54b2c93f336cfb0b00608c28","releaseDate":"2015-01-11T19:04:31.031Z","is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"0.4.0","version":"0.4.0"}],"current_version":{"version_clean":"0.4.0","version":"0.4.0"},"oauth":{"enabled":false},"api":{"name":"","url":"","contenttype":"form","auth":"","explorer":true,"proxyEnabled":true,"jwt":false,"authextra":[],"headers":[],"object_definitions":[]},"apiAlt":[],"plan_details":{"name":"Documentation (Old)","is_active":false,"cost":19,"versions":3,"custom_domain":false,"custom_pages":false,"whitelabel":false,"errors":false,"password":false,"landing_page":false,"themebuilder":true,"stylesheet":false,"javascript":false,"html":false,"extra_html":false,"admins":false},"intercom":"","intercom_secure_emailonly":false,"flags":{"allow_hub2":false,"hub2":false,"migrationRun":false,"oauth":false,"swagger":false,"correctnewlines":false,"speedyRender":false,"allowXFrame":false,"jwt":false,"hideGoogleAnalytics":false,"stripe":false,"disableDiscuss":false,"newApiExplorer":false,"autoSslGeneration":true},"asset_base_url":""}

{"_id":"54b2cb7687873d1f00dbebe5","slug":"what-is-bosco","title":"What is Bosco?","user":"54a3af95ad78941600ca2e2a","version":"54b2c93f336cfb0b00608c28","__v":9,"order":0,"excerpt":"","sync_unique":"","updates":["5a991cb317d31e0037e66a08"],"api":{"auth":"required","params":[],"results":{"codes":[]},"url":""},"category":"54b2c93f336cfb0b00608c29","createdAt":"2015-01-11T19:13:58.557Z","body":"Bosco is a utility knife to help manage the complexity that using microservices, which naturally results in a large number of code repositories, brings with it. Inspired by the Github 'setup', e.g. can a developer run one simple command and get up and running?\n\nSome of the things that Bosco likes to do for you:\n\n* Clone and pull a large number of Github repositories, that combined make up a larger system - you will always be up to date with your team.\n* Automatically link inter dependent projects (auto npm link).\n* Run projects - via either PM2 or Docker.\n* Minify static assets - javascript, html, images and css - serving them up locally as a pseudo CDN or pushing them to S3 for production.\n* Provide tools like multi-repository git grep, status etc.\n\nIt was built at TES to assist us with the journey of taking a number of teams with us on a journey towards micro services, but it can help with any project that is made up of a collection of Github repositories.\n\nFirst up:  [Getting Started](doc:getting-started)","link_external":false,"link_url":"","type":"basic","githubsync":"","hidden":false,"project":"54b2c91287873d1f00dbebdb","isReference":false,"next":{"pages":[]},"childrenPages":[]}

What is Bosco?

Bosco is a utility knife to help manage the complexity that using microservices, which naturally results in a large number of code repositories, brings with it. Inspired by the Github 'setup', e.g. can a developer run one simple command and get up and running? Some of the things that Bosco likes to do for you: * Clone and pull a large number of Github repositories, that combined make up a larger system - you will always be up to date with your team. * Automatically link inter dependent projects (auto npm link). * Run projects - via either PM2 or Docker. * Minify static assets - javascript, html, images and css - serving them up locally as a pseudo CDN or pushing them to S3 for production. * Provide tools like multi-repository git grep, status etc. It was built at TES to assist us with the journey of taking a number of teams with us on a journey towards micro services, but it can help with any project that is made up of a collection of Github repositories. First up: [Getting Started](doc:getting-started)

Fork me on GitHub