• Allowing your internal search engine to index Gitlab Issues, Commits and Wiki pages

    I've basically lived my life inside issue tracking systems - it used to be JIRA, and I had built tooling allowing effective indexing/mirroring of JIRA issues, but then Atlassian decided to all but do away with on-prem users. So, like many others, I moved over to Gitlab instead.

    As a product, Gitlab's great: it's got project lifecycle management, issue tracking, wiki support and even a container registry baked straight into it.

    However, it's indexability is basically non existent - even if you have projects marked as public, significant parts of pages are fetched by javascript, so a crawler can't index things like issue references (no, I'm not kidding) unless they execute javascript. It's like they reverse search engine optimised...

    It's not just on-prem Gitlab either, it also affects their cloud offering.

    Search within Gitlab is excellent, but this is of little use if you have things spread across systems and want to search from a single central point (to be fair to Gitlab, their idea is that everything you do should be within their solution, but life rarely actually works that way).

    This documentation details how to use my new tooling (rudimentary as it currently is) to expose an indexable version of your Gitlab life. Although this is focused on an on-prem install, this tool should work with their cloud offering too, as the APIs are the same (but I haven't tested against it).

  • Allowing your Internal Search Engine to Index JIRA Issues

    I use a number of tools on my network, including a private JIRA install (i.e. you need to log in to view anything) and the Sphider PHP search engine (I've generated a lot of documentation over the years).

    Unfortunately the two aren't exactly compatible, as Sphider has no way to log into JIRA, but I wanted my JIRA issues and comments to be indexed so that relevant items can be included in my search results. One option would be to set JIRA to public mode, but I'd rather maintain the need to log in.

    So instead I created a simple PHP script - JIRA Issue Listing - to generate a list that Sphider could index, but would redirect 'real' users to the relevant issue on JIRA.

    This post is the documentation for that script

  • Republished: Manual Database Retrieval Script for ZoneAlarm

    Originally published on Benscomputer.no-ip.org Jun 2008 (Note: Attached Script still works at time of Republishing)


    I was browsing the net earlier to try and find an answer to whether it is possible to manually download the ZoneAlarm Anti-Virus signatures. For those wondering why you would want to, standalone machines can't access the net to download the signatures, but are still subject to users with CD's and USB sticks. The easy way would be to update ZoneAlarm on a net connected PC and then copy the files from C:\Windows\System32\Zonelabs\avsys\base\ but if you don't have access to one, but do have a Linux Box then the script I have written will fetch the files for you (there are a lot, but they only add up to about 30 megs at time of writing).