{"id":273,"date":"2015-12-24T18:03:27","date_gmt":"2015-12-24T17:03:27","guid":{"rendered":"https:\/\/blog.unetresgrossebite.com\/?p=273"},"modified":"2015-12-26T20:10:09","modified_gmt":"2015-12-26T19:10:09","slug":"patchdashboard","status":"publish","type":"post","link":"https:\/\/blog.unetresgrossebite.com\/?p=273","title":{"rendered":"PatchDashboard"},"content":{"rendered":"<p>Having used <a href=\"https:\/\/blog.unetresgrossebite.com\/?p=101\">pakiti<\/a> by the past, and intending to setup some version tracking system to keep an eye on a setup I started managing recently, I was looking for an alternative that would work out of the box &#8211; which is my main grudge against pakiti2, I have a large set of patches, scripts, database init dump, which makes it pretty impractical to setup from scratch.<\/p>\n<p>Investigating on the subject, I stumbled upon several rpm-based solutions, such as <a href=\"http:\/\/www.pulpproject.org\/\">PulpProject<\/a>, <a href=\"http:\/\/spacewalk.redhat.com\/\">SpaceWalk<\/a> or its successor: <a href=\"http:\/\/www.katello.org\/\">Katello<\/a>.<\/p>\n<div id=\"attachment_277\" style=\"width: 310px\" class=\"wp-caption alignleft\"><a href=\"https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-KO.png\" rel=\"attachment wp-att-277\"><img aria-describedby=\"caption-attachment-277\" decoding=\"async\" loading=\"lazy\" class=\"size-medium wp-image-277\" src=\"https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-KO-300x132.png\" alt=\"PatchDashboard frontpage\" width=\"300\" height=\"132\" srcset=\"https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-KO-300x132.png 300w, https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-KO-768x338.png 768w, https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-KO-1024x450.png 1024w, https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-KO.png 1364w\" sizes=\"(max-width: 300px) 100vw, 300px\" \/><\/a><p id=\"caption-attachment-277\" class=\"wp-caption-text\">PatchDashboard frontpage<\/p><\/div>\n<p>Although\u00a0the setup I&#8217;m working with today is build around Ubuntu, and a couple Debian. Which is how I ended up trying out <a href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\">PatchDashboard<\/a>.<\/p>\n<p>There&#8217;s a <a class=\"issue-link js-issue-link\" href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/issues\/14\" data-url=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/issues\/14\" data-id=\"123800233\" data-error-text=\"Failed to load issue title\" data-permission-text=\"Issue title is private\">couple\u00a0stuff<\/a>\u00a0I noticed during install on Debian jessie. A detail\u00a0<a class=\"issue-link js-issue-link\" href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/issues\/21\" data-url=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/issues\/21\" data-id=\"123814773\" data-error-text=\"Failed to load issue title\" data-permission-text=\"Issue title is private\">regarding http proxies<\/a>\u00a0if you have such. And ultimately, <a href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/issues\/31\">a certificate error<\/a> on <a href=\"https:\/\/patchdashboard.com\/\">their website<\/a>.<br \/>\nI also\u00a0sent a few pull requests dealing with php errors, mostly cosmetic\u00a0[<a class=\"issue-link js-issue-link\" href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/15\" data-url=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/issues\/15\" data-id=\"123802296\" data-error-text=\"Failed to load issue title\" data-permission-text=\"Issue title is private\">1<\/a>, <a class=\"issue-link js-issue-link\" href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/17\" data-url=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/issues\/17\" data-id=\"123810480\" data-error-text=\"Failed to load issue title\" data-permission-text=\"Issue title is private\">2<\/a>,\u00a0<a class=\"issue-link js-issue-link\" title=\"Fix undefined variable error message\" href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/18\" data-id=\"123811619\" data-error-text=\"Failed to load issue title\" data-permission-text=\"Issue title is private\">3<\/a>, <a href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/25\">4<\/a>, <a href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/26\">5<\/a>, <a href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/27\">6<\/a>], some\u00a0more practical [<a class=\"issue-link js-issue-link\" href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/19\" data-url=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/issues\/19\" data-id=\"123812347\" data-error-text=\"Failed to load issue title\" data-permission-text=\"Issue title is private\">7<\/a>,\u00a0<a class=\"issue-link js-issue-link\" title=\"an other couple undefined variables\" href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/20\" data-id=\"123814071\" data-error-text=\"Failed to load issue title\" data-permission-text=\"Issue title is private\">8<\/a>, <a href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/29\">9<\/a>, <a href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/30\">10<\/a>], and adding Debian jessie to their database init script [<a href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/22\">11<\/a>, <a href=\"https:\/\/github.com\/PatchDashboard\/patchdashboard\/pull\/23\">12<\/a>].<\/p>\n<p>Having dealt with that, everything works pretty much as expected.<\/p>\n<div id=\"attachment_278\" style=\"width: 310px\" class=\"wp-caption alignright\"><a href=\"https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-list-vulns.png\" rel=\"attachment wp-att-278\"><img aria-describedby=\"caption-attachment-278\" decoding=\"async\" loading=\"lazy\" class=\"size-medium wp-image-278\" src=\"https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-list-vulns-300x135.png\" alt=\"PatchDashboard list vulnerable packages\" width=\"300\" height=\"135\" srcset=\"https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-list-vulns-300x135.png 300w, https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-list-vulns-768x345.png 768w, https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-list-vulns-1024x460.png 1024w, https:\/\/blog.unetresgrossebite.com\/wp-content\/uploads\/2015\/12\/patchdashboard-list-vulns.png 1349w\" sizes=\"(max-width: 300px) 100vw, 300px\" \/><\/a><p id=\"caption-attachment-278\" class=\"wp-caption-text\">PatchDashboard list vulnerable packages<\/p><\/div>\n<p>Next stuff I added to my setup, is some patch listing installed nodejs packages, and known vulnerabilities (according to <a href=\"https:\/\/snyk.io\/\">snyk<\/a>).<\/p>\n<p>I&#8217;m not sure these would be relevant enough to send a pull request, this is a whole new feature, that only makes sense for those hosting nodejs-based apps.<br \/>\nNote I\u00a0did\u00a0publish the <a href=\"https:\/\/github.com\/faust64\/patchdashboard\/commit\/0408b81118a4dcbf4503129ca03a8c3607d569af\">corresponding changes<\/a>, yet only to\u00a0<a href=\"https:\/\/github.com\/faust64\/patchdashboard\/tree\/peerio\">my fork on github<\/a>,<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Having used pakiti by the past, and intending to setup some version tracking system to keep an eye on a setup I started managing recently, I was looking for an alternative that would work out of the box &#8211; which is my main grudge against pakiti2, I have a large set of patches, scripts, database [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[8,10,6],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/273"}],"collection":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=273"}],"version-history":[{"count":13,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/273\/revisions"}],"predecessor-version":[{"id":292,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/273\/revisions\/292"}],"wp:attachment":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=273"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=273"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=273"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}