
{"id":23,"date":"2013-03-26T13:11:40","date_gmt":"2013-03-26T13:11:40","guid":{"rendered":"http:\/\/pages.charlotte.edu\/mark-hamrick\/?p=23"},"modified":"2013-03-26T13:11:40","modified_gmt":"2013-03-26T13:11:40","slug":"calling-in-the-librarian-for-puppet","status":"publish","type":"post","link":"http:\/\/pages.charlotte.edu\/mark-hamrick\/blog\/2013\/03\/26\/calling-in-the-librarian-for-puppet\/","title":{"rendered":"Calling in the Librarian for Puppet"},"content":{"rendered":"<p>Users running a puppet server can quickly find that module management is a significant issue.\u00a0 Modules can come from a variety of sources, including puppet forge, local git repos and if someone gets it working Boxen.<\/p>\n<p>The answer to this problem is librarian-puppet.\u00a0\u00a0 Using a file called PuppetFile that defines all or your modules, and it takes over your modules directory.\u00a0 Link to the project is below.<\/p>\n<p><a href=\"https:\/\/github.com\/rodjek\/librarian-puppet\">https:\/\/github.com\/rodjek\/librarian-puppet<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Users running a puppet server can quickly find that module management is a significant issue.\u00a0 Modules can come from a variety of sources, including puppet forge, local git repos and if someone gets it working Boxen. The answer to this problem is librarian-puppet.\u00a0\u00a0 Using a file called PuppetFile that defines all or your modules, and [&hellip;]<\/p>\n","protected":false},"author":22,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-23","post","type-post","status-publish","format-standard","hentry","category-updates"],"_links":{"self":[{"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/posts\/23","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/comments?post=23"}],"version-history":[{"count":2,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/posts\/23\/revisions"}],"predecessor-version":[{"id":25,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/posts\/23\/revisions\/25"}],"wp:attachment":[{"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/media?parent=23"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/categories?post=23"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/pages.charlotte.edu\/mark-hamrick\/wp-json\/wp\/v2\/tags?post=23"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}