Alfred

Due to the flexibiilty of Django , I will often use it in places that are not a normal web app. A combination of the Django ORM and admin commands makes a Django project a useful place to collect useful scripts. In the past I would often add things to Cron, but due to the tasks framework I have started to add some jobs there. To make it even easier to call tasks, I hooked up Alfred to my Django project.

While most code forges have a decent way of navigating code, going back and forth becomes tedious and it can often be easier to check things offline. The trick I use on my machine, is to combine alfred and a alfred-repos plugin for helping make things easier to search.

Using my own forked version to add some icons, I have a configuration file that looks like this.

{
  "__workflow_last_version": "4.1.0",
  "app_alt": "Terminal",
  "app_cmd": "Gitup",
  "app_default": "Visual Studio Code",
  "app_ctrl": "Browser",
  "global_exclude_patterns": [],
  "search_dirs": [
    // Projects is self explanitory
    {
      "depth": 2,
      "path": "~/Projects",
      "icon": "project.png"
    },
    // References is any 3rd party code I might want to view
    {
      "depth": 2,
      "path": "~/References",
      "icon": "references.png"
    },
    // I keep some documents in git as well
    {
      "depth": 2,
      "icon": "document.png",
      "path": "~/Documents"
    }
  ]
}

Adding icons gives me an extra visual hint what type of repo is found from Alfred.

I’ve been using alfred on my macs for quite a number of years. I don’t remember how I first found out about it, but it’s nearly always the first thing I install on new machines. Should I move to Linux, I am certainly going to need to find an equivalent and onagre looks like it might be one potential replacement. Inspired by a random comment on mastodon, I thought it would be interesting to write about my most commonly used workflows.