Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://akrabat.com/feed/

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. >
  9.  
  10. <channel>
  11. <title>Rob Allen</title>
  12. <atom:link href="https://akrabat.com/feed/" rel="self" type="application/rss+xml" />
  13. <link>https://akrabat.com</link>
  14. <description>Pragmatism in today&#039;s world</description>
  15. <lastBuildDate>Tue, 19 Aug 2025 12:30:31 +0000</lastBuildDate>
  16. <language>en-US</language>
  17. <sy:updatePeriod>
  18. hourly </sy:updatePeriod>
  19. <sy:updateFrequency>
  20. 1 </sy:updateFrequency>
  21. <generator>https://wordpress.org/?v=6.8.2</generator>
  22. <item>
  23. <title>Converting JWKS JSON to PEM using Python</title>
  24. <link>https://akrabat.com/converting-jwks-json-to-pem-using-python/</link>
  25. <comments>https://akrabat.com/converting-jwks-json-to-pem-using-python/#respond</comments>
  27. <dc:creator><![CDATA[Rob]]></dc:creator>
  28. <pubDate>Tue, 09 Sep 2025 10:00:00 +0000</pubDate>
  29. <category><![CDATA[Command Line]]></category>
  30. <category><![CDATA[Python]]></category>
  31. <guid isPermaLink="false">https://akrabat.com/?p=7484</guid>
  32.  
  33. <description><![CDATA[Following on from my earlier exploration of JWKS (RFC7517), I found myself needing to convert the JWKS into PEM format. This time I turned to Python with my preference of using uv with inline script metadata and created jwks-to-pem.py. The really nice thing about inline script metadata is that we can use the cryptography package to do all the hard work with RSA and serialisation. We just have to remember that the base64 encoded values… <a href="https://akrabat.com/converting-jwks-json-to-pem-using-python/">continue reading</a>.]]></description>
  34. <content:encoded><![CDATA[<p>Following on from my <a href="https://akrabat.com/creating-jwks-json-file-in-php/">earlier exploration of JWKS</a> (<a href="https://www.rfc-editor.org/rfc/rfc7517">RFC7517</a>), I found myself needing to convert the JWKS into PEM format.</p>
  35. <p>This time I turned to Python with my preference of using <a href="https://github.com/astral-sh/uv">uv</a> with <a href="https://akrabat.com/defining-python-dependencies-at-the-top-of-the-file/">inline script metadata</a> and created <a href="#script"><tt>jwks-to-pem.py</tt></a>.</p>
  36. <p>The really nice thing about inline script metadata is that we can use the <a href="https://pypi.org/project/cryptography/">cryptography package</a> to do all the hard work with RSA and serialisation. We just have to remember that the base64 encoded values are <a href="https://datatracker.ietf.org/doc/html/rfc4648#section-5">base64 URL encoded</a> and account for it.</p>
  37. <p>As a single file python script, I make it executable with <tt>chmod +x jwks-to-pem.py</tt> and made it so that I can pipe the output of a <a href="https://curl.se">curl</a> call to it, or pass in a JSON file. I prefer to use the <tt>curl</tt> solution though with:</p>
  38. <pre>
  39. curl -s https://example.com/.well-known/jwks.json | jwks-to-pem.py
  40. </pre>
  41. <h3>Example</h3>
  42. <p>Here's an example from the <a href="https://developer.api.apps.cam.ac.uk/docs/oauth2/1/routes/.well-known/jwks.json/get">University of Cambridge</a>.</p>
  43. <p>On the day I wrote this article, the JWKS looks like this:</p>
  44. <pre>
  45. $ curl -s https://api.apps.cam.ac.uk/oauth2/v1/.well-known/jwks.json
  46. {
  47.  "keys": [
  48.    {
  49.      "alg": "RS256",
  50.      "e": "AQAB",
  51.      "n": "6kKjjctVPalX0ypJ2irwog8xIXS9JTABqrSnK_n3YJ4q0aH2-1bjGbWz8p1CaCUqDxQSDuqzvOgMdNGvZrxlNJ-G8hfc39jrb_KnB0T3ZsuxFz6X0mDzmHhdiPjSDK3M0syC4qg5_PB7xwKail5VWOcY0SypIYCPD6Ct5DGnQ_XONGXIVG7eaJAHdxJp2BOz0n3BVEFnZUgM5JcfGrSFfGqb0ZotX2AblwjZKQc58E0EVVykJw8gxW1Bob8rbaVXlMHssfY-9Jx0zua7ZrjO5C4OMmt9J6zYbVnGVwf62ehGtcLSP6iCG4_XM2sAMQwqJnPBss0U9WwDERk17FMHvb_FBwxAFxRygd0DclWmQmCYr5uFYck57KGARtyoxrNNAf4AFUHuObjbV24TyInYEgMhKi3SAML_4ke3dbbG-mjchXPN9OqNd4fydnQIP39WFHmFNk_nIlqvYnALI4xPE-w09T9jCvjU8hYHHlVMRvRluBnUzJkFnxLse5W-agC6ITe3wYvKH7SHVp6MYQWVD_0I2rCLV4gqjSpXzKIMs5eejjTQQq0VYumgL_f1ETvzDoewzXLOC8GGu2LZDwDbP0ea6DchReWjZfj4nJx23uQyGAj1h_uPI1jCd9oeJhbN8jFz2ltYgXYBp51qdSzsbtdec9BPPBVeXjI--c0AWU8",
  52.      "kid": "70e0ed3c",
  53.      "kty": "RSA",
  54.      "use": "sig"
  55.    }
  56.  ]
  57. }
  58. </pre>
  59. <p>They very kindly pretty-print it too!</p>
  60. <p>We can then get the PEM version by piping to <tt>jwks-to-pem.py</tt>:</p>
  61. <pre>
  62. $ curl -s https://api.apps.cam.ac.uk/oauth2/v1/.well-known/jwks.json | jwks-to-pem.py
  63. # Key 0 (kid: 70e0ed3c)
  64. -----BEGIN PUBLIC KEY-----
  65. MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA6kKjjctVPalX0ypJ2irw
  66. og8xIXS9JTABqrSnK/n3YJ4q0aH2+1bjGbWz8p1CaCUqDxQSDuqzvOgMdNGvZrxl
  67. NJ+G8hfc39jrb/KnB0T3ZsuxFz6X0mDzmHhdiPjSDK3M0syC4qg5/PB7xwKail5V
  68. WOcY0SypIYCPD6Ct5DGnQ/XONGXIVG7eaJAHdxJp2BOz0n3BVEFnZUgM5JcfGrSF
  69. fGqb0ZotX2AblwjZKQc58E0EVVykJw8gxW1Bob8rbaVXlMHssfY+9Jx0zua7ZrjO
  70. 5C4OMmt9J6zYbVnGVwf62ehGtcLSP6iCG4/XM2sAMQwqJnPBss0U9WwDERk17FMH
  71. vb/FBwxAFxRygd0DclWmQmCYr5uFYck57KGARtyoxrNNAf4AFUHuObjbV24TyInY
  72. EgMhKi3SAML/4ke3dbbG+mjchXPN9OqNd4fydnQIP39WFHmFNk/nIlqvYnALI4xP
  73. E+w09T9jCvjU8hYHHlVMRvRluBnUzJkFnxLse5W+agC6ITe3wYvKH7SHVp6MYQWV
  74. D/0I2rCLV4gqjSpXzKIMs5eejjTQQq0VYumgL/f1ETvzDoewzXLOC8GGu2LZDwDb
  75. P0ea6DchReWjZfj4nJx23uQyGAj1h/uPI1jCd9oeJhbN8jFz2ltYgXYBp51qdSzs
  76. btdec9BPPBVeXjI++c0AWU8CAwEAAQ==
  77. -----END PUBLIC KEY-----
  78.  
  79. </pre>
  80. <h3>The script</h3>
  81. <p>This is the script in case anyone else finds it useful:</p>
  82. <pre lang="python" id="script">
  83. #!/usr/bin/env -S uv run --script --quiet
  84. # /// script
  85. # dependencies = [
  86. #   "cryptography",
  87. # ]
  88. # ///
  89.  
  90. """Convert JWK keys to PEM format.
  91.  
  92. This script reads .well-known/jwks.json and outputs PEM encoded versions
  93. of the public keys in that file.
  94.  
  95. Usage:
  96.    curl -s https://example.com/.well-known/jwks.json | jwks-to-pem.py
  97.    uv run jwks-to-pem.py jwks.json
  98.    uv run jwks-to-pem.py < jwks.json
  99.  
  100. Requirements:
  101.    - uv (https://github.com/astral-sh/uv)
  102.    - cryptography library
  103.  
  104. Author:
  105.    Rob Allen <rob@akrabat.com>
  106.    Copyright 2025
  107.  
  108. License:
  109.    MIT License - https://opensource.org/licenses/MIT
  110. """
  111.  
  112. import json
  113. import base64
  114. import sys
  115. from cryptography.hazmat.primitives import serialization
  116. from cryptography.hazmat.primitives.asymmetric import rsa
  117.  
  118. def base64url_decode(data):
  119.    """Decode base64url to bytes"""
  120.    # Add padding if needed
  121.    padding = 4 - len(data) % 4
  122.    if padding != 4:
  123.        data += '=' * padding
  124.  
  125.    # Replace URL-safe chars
  126.    data = data.replace('-', '+').replace('_', '/')
  127.  
  128.    # Decode
  129.    return base64.b64decode(data)
  130.  
  131. def jwk_to_pem(jwk_key):
  132.    """Convert JWK to PEM format"""
  133.    if jwk_key['kty'] != 'RSA':
  134.        raise ValueError("Only RSA keys are supported")
  135.  
  136.    # Decode the modulus (n) and exponent (e) to int
  137.    n = int.from_bytes(base64url_decode(jwk_key['n']), 'big')
  138.    e = int.from_bytes(base64url_decode(jwk_key['e']), 'big')
  139.  
  140.    # Create RSA public key
  141.    public_key = rsa.RSAPublicNumbers(e, n).public_key()
  142.  
  143.    # Serialize to PEM
  144.    pem = public_key.public_bytes(
  145.        encoding=serialization.Encoding.PEM,
  146.        format=serialization.PublicFormat.SubjectPublicKeyInfo
  147.    )
  148.    return pem.decode()
  149.  
  150. def main():
  151.    if len(sys.argv) > 2:
  152.        print("Usage: jwk_to_pem.py [jwks.json]")
  153.        print("If no file is provided, reads from stdin")
  154.        sys.exit(1)
  155.  
  156.    if len(sys.argv) == 2 and sys.argv[1] != '-':
  157.        # Read from file
  158.        with open(sys.argv[1], 'r') as f:
  159.            jwks = json.load(f)
  160.    else:
  161.        # Read from stdin
  162.        jwks = json.load(sys.stdin)
  163.  
  164.    # Convert each key
  165.    for i, key in enumerate(jwks['keys']):
  166.        kid = key.get('kid', f'key-{i}')
  167.        print(f"# Key {i} (kid: {kid})")
  168.        print(jwk_to_pem(key))
  169.  
  170. if __name__ == "__main__":
  171.    main()
  172. </pre>
  173. ]]></content:encoded>
  175. <wfw:commentRss>https://akrabat.com/converting-jwks-json-to-pem-using-python/feed/</wfw:commentRss>
  176. <slash:comments>0</slash:comments>
  179. </item>
  180. <item>
  181. <title>Stop in-place editing of bash history items</title>
  182. <link>https://akrabat.com/stop-in-place-editing-of-bash-history-items/</link>
  183. <comments>https://akrabat.com/stop-in-place-editing-of-bash-history-items/#comments</comments>
  185. <dc:creator><![CDATA[Rob]]></dc:creator>
  186. <pubDate>Tue, 02 Sep 2025 10:00:00 +0000</pubDate>
  187. <category><![CDATA[Command Line]]></category>
  188. <category><![CDATA[Shell Scripting]]></category>
  189. <guid isPermaLink="false">https://akrabat.com/?p=7480</guid>
  190.  
  191. <description><![CDATA[Recently, since getting a new computer, I've noticed that I've been losing bash history items and it took a while to work out what was going on, though I'm still not completely sure as it never seemed to be so much of a problem. I regularly use the up and down keys with context specific history. For example, I will type ma and then press up to search back through all the make commands I've… <a href="https://akrabat.com/stop-in-place-editing-of-bash-history-items/">continue reading</a>.]]></description>
  192. <content:encoded><![CDATA[<p>Recently, since getting a new computer, I've noticed that I've been losing bash history items and it took a while to work out what was going on, though I'm still not completely sure as it never seemed to be so much of a problem. </p>
  193. <p>I regularly use the up and down keys with <a href="/context-specific-history-at-the-bash-prompt/">context specific history</a>. For example, I will type <tt>ma</tt> and then press up to search back through all the <tt>make</tt> commands I've used recently and then press enter to run it. </p>
  194. <p>Sometimes, I'll realise that I don't actually want this command and edit it and press enter. Sometimes I'll decide halfway through editing that really I should use a <tt>docker compose</tt> command instead and I'll just back out of my edit via some key stroke that works. I'm not sure what I do here though, probably up/down, or maybe ctrl+c. Whatever I do, sometimes, the history for that line is now my edited mess and not the original command. Then later, when I go to try and find it via the up arrow, it's missing.</p>
  195. <p>This happened infrequently enough that I thought I was misremembering what was in the history, or that maybe it was another tab I was thinking about.</p>
  196. <p>I never want the bash history to be editable; if I cancel out, then I want it back to what it was.</p>
  197. <h2>Fixing with revert-all-at-newline</h2>
  198. <p>This finally annoyed me enough that I sat down with the Internet to work out how to fix it with the <tt>revert-all-at-newline</tt> setting.</p>
  199. <p>The revert-all-at-newline option in bash controls whether readline reverts any changes made to a history line when you press Enter. Note that this is part of readline's behavior, so it affects command line editing in bash and other programs that use <a href="https://en.wikipedia.org/wiki/GNU_Readline">readline</a>.</p>
  200. <p>The simplest thing is to add this to <tt>.bashrc</tt>:</p>
  201. <pre lang="bash">
  202. bind 'set revert-all-at-newline on'
  203. </pre>
  204. <p>Alternatively, you can create a <tt>.inputrc</tt> file with this in it:</p>
  205. <pre>
  206. $include /etc/inputrc
  207. set revert-all-at-newline on
  208. </pre>
  209. <p>To view the current value of <tt>revert-all-at-newline</tt>, use: </p>
  210. <pre>
  211. bind -V | grep revert-all-at-newline
  212. </pre>
  213. <p>It solved my problem, and I've not yet found a case when I want it set the other way.</p>
  214. ]]></content:encoded>
  216. <wfw:commentRss>https://akrabat.com/stop-in-place-editing-of-bash-history-items/feed/</wfw:commentRss>
  217. <slash:comments>1</slash:comments>
  220. </item>
  221. <item>
  222. <title>Extending an OpenAPI Component Schema</title>
  223. <link>https://akrabat.com/extending-an-openapi-component-schema/</link>
  224. <comments>https://akrabat.com/extending-an-openapi-component-schema/#respond</comments>
  226. <dc:creator><![CDATA[Rob]]></dc:creator>
  227. <pubDate>Tue, 26 Aug 2025 10:00:00 +0000</pubDate>
  228. <category><![CDATA[OpenAPI]]></category>
  229. <guid isPermaLink="false">https://akrabat.com/?p=7477</guid>
  230.  
  231. <description><![CDATA[One project that I'm working on uses RFC 9457 Problem Details for HTTP APIs for its error responses. In the OpenAPI spec, we can define this as a component and use in the relevant paths as appropriate: components: schemas: ProblemDetails: type: object properties: type: type: string format: uri-reference description: A URI reference that identifies the problem type default: about:blank example: https://example.com/probs/out-of-credit title: type: string description: A short, human-readable summary of the problem type example: You… <a href="https://akrabat.com/extending-an-openapi-component-schema/">continue reading</a>.]]></description>
  232. <content:encoded><![CDATA[<p>One project that I'm working on uses <a href="https://www.rfc-editor.org/rfc/rfc9457.html">RFC 9457 Problem Details for HTTP APIs </a> for its error responses.</p>
  233. <p>In the OpenAPI spec, we can define this as a component and use in the relevant paths as appropriate:</p>
  234. <pre lang="yaml">
  235. components:
  236.  schemas:
  237.    ProblemDetails:
  238.      type: object
  239.      properties:
  240.        type:
  241.          type: string
  242.          format: uri-reference
  243.          description: A URI reference that identifies the problem type
  244.          default: about:blank
  245.          example: https://example.com/probs/out-of-credit
  246.        title:
  247.          type: string
  248.          description: A short, human-readable summary of the problem type
  249.          example: You do not have enough credit.
  250.        status:
  251.          type: integer
  252.          format: int32
  253.          description: The HTTP status code for this occurrence of the problem
  254.          minimum: 100
  255.          maximum: 599
  256.          example: 403
  257.        detail:
  258.          type: string
  259.          description: A human-readable explanation specific to this occurrence of the problem
  260.          example: Your current balance is 30, but that costs 50.
  261.        instance:
  262.          type: string
  263.          format: uri-reference
  264.          description: A URI reference that identifies the specific occurrence of the problem
  265.          example: /account/12345/msgs/abc
  266.      additionalProperties: true
  267. </pre>
  268. <p>When we return a validation error, we add an <tt>errors</tt> property. Rather than repeating the <tt>ProblemDetails</tt> properties into <tt>ValidationError</tt>, we can add the <tt>errors</tt> using <a href="https://json-schema.org/understanding-json-schema/reference/combining#allOf"><tt>allOf</tt></a>:</p>
  269. <pre lang="yaml">
  270.    ValidationError:
  271.      allOf:
  272.        - $ref: '#/components/schemas/ProblemDetails'
  273.        - type: object
  274.          properties:
  275.            errors:
  276.              type: object
  277.              description: Field-specific validation error messages
  278.              additionalProperties:
  279.                type: string
  280.              example:
  281.                name: "name must be provided"
  282.                dateOfBirth: "date must be in the past"
  283. </pre>
  284. <p>This is quite handy!</p>
  285. ]]></content:encoded>
  287. <wfw:commentRss>https://akrabat.com/extending-an-openapi-component-schema/feed/</wfw:commentRss>
  288. <slash:comments>0</slash:comments>
  291. </item>
  292. <item>
  293. <title>Saving the current URL to a Note</title>
  294. <link>https://akrabat.com/saving-the-current-url-to-a-note/</link>
  295. <comments>https://akrabat.com/saving-the-current-url-to-a-note/#respond</comments>
  297. <dc:creator><![CDATA[Rob]]></dc:creator>
  298. <pubDate>Tue, 19 Aug 2025 10:00:00 +0000</pubDate>
  299. <category><![CDATA[Mac]]></category>
  300. <category><![CDATA[Shortcuts]]></category>
  301. <guid isPermaLink="false">https://akrabat.com/?p=7467</guid>
  302.  
  303. <description><![CDATA[Inspired by John Gruber mentioning on the Cortex podcast that he has a shortcut that saves links to a note in Tot, I thought I'd do something similar for saving to a note in Apple Notes. I want to store as a bullet item containing the name of the page, the link and the date. Something like this: (Funny that the spellchecker doesn't know that Thu is the short form for Thursday) The Save Links… <a href="https://akrabat.com/saving-the-current-url-to-a-note/">continue reading</a>.]]></description>
  304. <content:encoded><![CDATA[<p>Inspired by John Gruber mentioning on the <a href="https://www.relay.fm/cortex/169">Cortex podcast</a> that he has a shortcut that saves links to a note in <a href="https://tot.rocks">Tot</a>, I thought I'd do something similar for saving to a note in Apple Notes.</p>
  305. <p>I want to store as a bullet item containing the name of the page, the link and the date. Something like this:</p>
  306. <picture><source  
  307. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025saved-link-text-dark.png"
  308.        media="(prefers-color-scheme: dark)"
  309.    /><source
  310. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025saved-link-text-light.png"
  311.        media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)"
  312.    /><br />
  313.    <img decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025saved-link-text-light.png" loading="lazy" alt="Saved link text light." class="border" width="408"/>
  314. </picture>
  315. <p>(Funny that the spellchecker doesn't know that Thu is the short form for Thursday)</p>
  316. <h2>The <em>Save Links to Notes</em> Shortcut</h2>
  317. <p>This is the shortcut that I created to do it:
  318. <picture><source  
  319. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025save-links-to-notes-shortcut-dark.png"
  320.        media="(prefers-color-scheme: dark)"
  321.    /><source
  322. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025save-links-to-notes-shortcut-light.png"
  323.        media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)"
  324.    /><br />
  325.    <img decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025save-links-to-notes-shortcut-light.png" loading="lazy" alt="Save links to notes shortcut light." class="noborder" width="558"/>
  326. </picture>
  327. <p>You can download it here:<br />
  328. <a href="https://www.icloud.com/shortcuts/6c12e888f9da431d9977985b229d636b">https://www.icloud.com/shortcuts/6c12e888f9da431d9977985b229d636b</a></p>
  329. <h2>Breaking down the actions</h2>
  330. <p>To get the URL into the shortcut, we want:</p>
  331. <ul>
  332. <li><em>Show in Share Sheet</em> so that it's available on iOS/iPadOS</li>
  333. <li><em>Receive What's Onscreen</em> so that when a browser is focussed on Mac, it finds the URL</li>
  334. <li><em>Use as a Quick Action</em> so that we can assign a keyboard shortcut (<tt style="font-family: sans-serif">⌃⌥⌘U</tt> in case)</li>
  335. </ul>
  336. <p>We can then use <em>Get Contents of web page</em> along with <em>Get Details of Safari Web Page</em> to get the pages's title which Shortcuts calls <em>Name</em> for some reason.</p>
  337. <p>There's an action for <em>Current Date</em>, so we add that to get the variable.</p>
  338. <p>Creating formatted text in a note is a little involved. Firstly we use a <em>Text</em> action to set out the Markdown that we want. I used the date format <tt>EEE, dd MMM yyyy</tt> as it's short and clear to me.</p>
  339. <p>There's a <em>Make Rich Text from Markdown</em> action which processes the Markdown for us, but if you just append it to the note, it doesn't work. The workaround is to add it to a <em>List</em> action and then append the list to the note. </p>
  340. <h2>That's it</h2>
  341. <p>All we need to do now is show a notification including the <tt>Shortcut Input</tt> variable as that's the URL that we've just saved.
  342. <picture><source  
  343. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025save-links-to-notes-notification-dark.png"
  344.        media="(prefers-color-scheme: dark)"
  345.    /><source
  346. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025save-links-to-notes-notification-light.png"
  347.        media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)"
  348.    /><br />
  349.    <img decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025save-links-to-notes-notification-light.png" loading="lazy" alt="Save links to notes notification light." class="noborder" width="376"/>
  350. </picture>
  351. <p>With this shortcut, I can add a new entry to my note from both my Mac, iPad and iPhone with minimal effort. </p>
  352. <p>I like it.</p>
  353. ]]></content:encoded>
  355. <wfw:commentRss>https://akrabat.com/saving-the-current-url-to-a-note/feed/</wfw:commentRss>
  356. <slash:comments>0</slash:comments>
  359. </item>
  360. <item>
  361. <title>Accessing Longplay info for SwiftBar</title>
  362. <link>https://akrabat.com/accessing-longplay-info-for-swiftbar/</link>
  363. <comments>https://akrabat.com/accessing-longplay-info-for-swiftbar/#respond</comments>
  365. <dc:creator><![CDATA[Rob]]></dc:creator>
  366. <pubDate>Tue, 12 Aug 2025 10:00:00 +0000</pubDate>
  367. <category><![CDATA[Mac]]></category>
  368. <guid isPermaLink="false">https://akrabat.com/?p=7447</guid>
  369.  
  370. <description><![CDATA[One app that I find incredibly useful is SwiftBar and one use I have is to display track info for the currently playing song in Apple Music. SwiftBar plugins work as shell scripts that execute on a timer and echo specially formatted text which SwiftBar then turns into an item on the menu bar with an attached menu I use a heavily modified Now Playing plugin that was originally written by Adam Kenyon, so all… <a href="https://akrabat.com/accessing-longplay-info-for-swiftbar/">continue reading</a>.]]></description>
  371. <content:encoded><![CDATA[<p>One app that I find incredibly useful is <a href="https://github.com/swiftbar/SwiftBar">SwiftBar</a> and one use I have is to display track info for the currently playing song in Apple Music.</p>
  372. <p>SwiftBar plugins work as shell scripts that execute on a timer and echo specially formatted text which SwiftBar then turns into an item on the menu bar with an attached menu</p>
  373. <p>I use a heavily modified <a href="https://github.com/matryer/xbar-plugins/blob/main/Music/nowplaying.5s.sh">Now Playing plugin</a> that was originally written by Adam Kenyon, so all the hard work was done by them.</p>
  374. <p>Recently, I've been using <a href="https://longplay.rocks">Longplay</a> to play albums and wanted the same functionality.</p>
  375. <p>Now Playing uses AppleScript to determine if a music player is playing and what the track info is:</p>
  376. <pre>
  377. app_playing=$(osascript -e "tell application \"$i\" to player state as string")
  378. </pre>
  379. <p>And</p>
  380. <pre>
  381. track=$(osascript -e "tell application \"$app\" to name of current track")
  382. artist=$(osascript -e "tell application \"$app\" to artist of current track")
  383. </pre>
  384. <p>When looking at adding Longplay, I was pleased to discover that it has AppleScript support, but perusing the Dictionary, I discovered that it doesn't support the features I need here.</p>
  385. <p>Upon emailing the developer, they very helpfully pointed out that Longplay also has Shortcuts support and that I could probably use that instead. They were right.</p>
  386. <p>I knocked up a couple of shortcuts:</p>
  387. <picture><source  
  388. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025longplay-status-dark.png"
  389.        media="(prefers-color-scheme: dark)"
  390.    /><source
  391. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025longplay-status-light.png"
  392.        media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)"
  393.    /><br />
  394.    <img decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025longplay-status-light.png" loading="lazy" alt="Longplay status Apple Shortcut" class="noborder" width="431"/>
  395. </picture>
  396. <p>and</p>
  397. <picture><source  
  398. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025longplay-now-playing-dark.png"
  399.        media="(prefers-color-scheme: dark)"
  400.    /><source
  401. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025longplay-now-playing-light.png"
  402.        media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)"
  403.    /><br />
  404.    <img decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025longplay-now-playing-light.png" loading="lazy" alt="Longplay now playing light." class="noborder" width="431"/>
  405. </picture>
  406. <p>With these set-up, I can now run them from the command line using <tt>shortcuts</tt>:</p>
  407. <pre>
  408. app_playing=$(shortcuts run "Longplay status");
  409. </pre>
  410. <p>This will set <tt>$app_playing</tt> to either "Yes" or "No" as strings as it is defined as boolean in Shortcuts.</p>
  411. <pre>
  412. track=$(shortcuts run "Longplay now playing");
  413. </pre>
  414. <p>This simply sets <tt>$track</tt> to the string of the currently playing track.</p>
  415. <h2>Updated Now Playing script</h2>
  416. <p>With the ability to get the info I needed from the command line, I <s>hacked</s> updated my copy of the Now Playing script and all is good.</p>
  417. <p>I've updated it a bit over the years, so I've uploaded my version to Gist: <a href="https://gist.github.com/akrabat/8bcfac9dfef5fd4e9b67ac5bb504ea7a">nowplaying.5s.sh</a>.</p>
  418. ]]></content:encoded>
  420. <wfw:commentRss>https://akrabat.com/accessing-longplay-info-for-swiftbar/feed/</wfw:commentRss>
  421. <slash:comments>0</slash:comments>
  424. </item>
  425. <item>
  426. <title>Responding to StreamDeck buttons with Keyboard Maestro</title>
  427. <link>https://akrabat.com/controlling-the-streamdeck-via-keyboard-maestro/</link>
  428. <comments>https://akrabat.com/controlling-the-streamdeck-via-keyboard-maestro/#respond</comments>
  430. <dc:creator><![CDATA[Rob]]></dc:creator>
  431. <pubDate>Tue, 05 Aug 2025 10:00:00 +0000</pubDate>
  432. <category><![CDATA[AppleScript]]></category>
  433. <category><![CDATA[Keyboard Maestro]]></category>
  434. <category><![CDATA[Mac]]></category>
  435. <guid isPermaLink="false">https://akrabat.com/?p=7440</guid>
  436.  
  437. <description><![CDATA[I run Apple Music on my Mac desktop and send the output to my HomePod minis. To control the volume, you need to manipulate the Apple Music volume slider rather than the global volume controls for the Mac. It's easier to press buttons than use a mouse, so I used Keyboard Maestro to respond to two buttons on my Stream Deck instead. This is possible because Keyboard Maestro has a Stream Deck Plugin, so you… <a href="https://akrabat.com/controlling-the-streamdeck-via-keyboard-maestro/">continue reading</a>.]]></description>
  438. <content:encoded><![CDATA[<p>I run Apple Music on my Mac desktop and send the output to my HomePod minis. To control the volume, you need to manipulate the Apple Music volume slider rather than the global volume controls for the Mac.</p>
  439. <p>It's easier to press buttons than use a mouse, so I used <a href="https://www.keyboardmaestro.com/">Keyboard Maestro</a> to respond to two buttons on my <a href="https://www.elgato.com/uk/en/p/stream-deck">Stream Deck</a> instead.</p>
  440. <p>This is possible because Keyboard Maestro has a <a href="https://marketplace.elgato.com/product/keyboard-maestro-35c7590b-b7fb-4be0-9e5d-9fd4b4c0f013">Stream Deck Plugin</a>, so you need to install that first.</p>
  441. <h2>Setting up the Stream Deck button</h2>
  442. <p>You can now assign Keyboard Maestro to a button in the Stream Deck software:</p>
  443. <p><img fetchpriority="high" decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025streamdeck-km-button.png" alt="Keyboard Maestro automation configuration interface showing a button setup with a speaker/volume icon. The interface displays fields for Title (empty), Button ID (R3C1), Virtual Row (3), and Virtual Column (1). The left side shows a black square button with white speaker and minus icons." title="streamdeck-km-button.png" border="0" width="500" height="239" /></p>
  444. <p>This is the configuration for my volume down button, as you can tell by the icon I chose. The Button ID defaults to the row and column number of where you have placed it on the Stream Deck.</p>
  445. <h2>Responding to the button in Keyboard Maestro</h2>
  446. <p>On the Keyboard Maestro side, we need a macro that is trigged by the Stream Deck button. This is easy to do as it looks like a USB device key and you can press the button the Stream Deck and Keyboard Maestro will recognise it and fill in the correct details.</p>
  447. <p><img decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025streamdeck-km-control.png" alt="Screenshot of an Keyboard Maestro automation interface showing a "Music volume down" macro. The trigger is a Stream Deck R3C1 button press with modifiers. The action executes AppleScript code that decreases the Music app's volume by 1, with a minimum volume of 0." title="streamdeck-km-control.png" border="0" width="500" height="529" /></p>
  448. <p>Upon clicking the button, we simply run some AppleScript to control the Music app's volume.</p>
  449. <h2>That's it</h2>
  450. <p>That's all there is to responding to a button on the Stream Deck on a Mac. In this case, I'm using AppleScript, but Keyboard Maestro lets you do practically anything on the computer!</p>
  451. ]]></content:encoded>
  453. <wfw:commentRss>https://akrabat.com/controlling-the-streamdeck-via-keyboard-maestro/feed/</wfw:commentRss>
  454. <slash:comments>0</slash:comments>
  457. </item>
  458. <item>
  459. <title>Step-debugging Docker Compose NestJS services</title>
  460. <link>https://akrabat.com/step-debugging-docker-compose-nestjs-services/</link>
  461. <comments>https://akrabat.com/step-debugging-docker-compose-nestjs-services/#respond</comments>
  463. <dc:creator><![CDATA[Rob]]></dc:creator>
  464. <pubDate>Tue, 29 Jul 2025 10:00:00 +0000</pubDate>
  465. <category><![CDATA[NodeJS]]></category>
  466. <category><![CDATA[TypeScript]]></category>
  467. <guid isPermaLink="false">https://akrabat.com/?p=7454</guid>
  468.  
  469. <description><![CDATA[I'm working on a NestJS project that uses monorepo mode. It consists of a number of separate microservice applications that each have their own Docker container that are managed in development using Docker Compose. I like step-debugging in my IDE and so needed to set it up for this application. This is what I did. The application setup Each service in our project has its own container in docker-compose.yaml and we use a reverse proxy to… <a href="https://akrabat.com/step-debugging-docker-compose-nestjs-services/">continue reading</a>.]]></description>
  470. <content:encoded><![CDATA[<p>I'm working on a <a href="https://nestjs.com">NestJS</a> project that uses <a href="https://docs.nestjs.com/cli/monorepo#monorepo-mode">monorepo mode</a>. It consists of a number of separate microservice applications that each have their own <a href="https://www.docker.com">Docker</a> container that are managed in development using <a href="https://docs.docker.com/compose/">Docker Compose</a>.</p>
  471. <p>I like step-debugging in my IDE and so needed to set it up for this application. This is what I did.</p>
  472. <h2>The application setup</h2>
  473. <p>Each service in our project has its own container in docker-compose.yaml and we use a reverse proxy to have a single endpoint that routes requests to the correct microservice. Each custom <tt>Dockerfile</tt> runs <tt>ppm run start:dev:{service name}></tt> which is defined in <tt>package.json</tt> like this:</p>
  474. <pre>
  475. "start:dev:service1": "nest start service1 --watch --tsc --watchOptions.poll=1000 --preserveWatchOutput",
  476. </pre>
  477. <p>Using <tt>--watchOptions.poll=1000</tt> is just more reliable when running in Docker with volumes mounted into the container. We also set the <tt>--preserveWatchOutput</tt> flag to ensure that the service doesn't take control of the terminal as this is unhelpful when you have multiple services in play.</p>
  478. <h2>Set the apps up for debugging</h2>
  479. <p>We need to make some modification for step debugging. Firstly, I created a set of <tt>start:debug:{service name}</tt> scripts in <tt>package.json</tt> that look like this:</p>
  480. <pre>
  481. "start:debug:service1": "nest start service1 --debug 0.0.0.0:9229 --watch --tsc --watchOptions.poll=1000 --preserveWatchOutput",
  482. </pre>
  483. <p>We enabled the <tt>--debug</tt> flag to enable node's <tt>--inspect</tt> flag so that port <tt>9229</tt> is available to the debugger. However, buy default this is bound to <tt>127.0.0.1</tt> which is not useful in a container, so we bind to <tt>0.0.0.0:9229</tt> so that it's available outside the container.</p>
  484. <p>Next, we need to our new <tt>start:debug:{service name}</tt> scripts and expose port 92229 to our local environment for each service. We do this in <tt>docker-compose.override.yaml</tt>:</p>
  485. <pre lang="yaml">
  486. services:
  487.  service1:
  488.    ports:
  489.      - "9230:9229"
  490.    command: pnpm run start:debug:service1
  491.  
  492.  service2:
  493.    ports:
  494.      - "9231:9229"
  495.    command: pnpm run start:debug:service2
  496. </pre>
  497. <p>I don't tend to like binding to the default port as that invariably confuses me when I run some test thing locally, so I've picked ports starting from <tt>9230</tt> onwards for my services.</p>
  498. <p>Running <tt>docker compose up</tt> will now start the containers.</p>
  499. <h2>Debugging in WebStorm</h2>
  500. <p>To set up <a href="https://www.jetbrains.com/webstorm/">WebStorm</a> for step debugging, create a <em>Run/Debug configuration</em> entry of type <tt>Attach to Node.js/Chrome</tt> for each container.</p>
  501. <p>The settings for service1 are:</p>
  502. <ul>
  503. <li>Name: Debug service1</li>
  504. <li>Host: localhost</li>
  505. <li>Port: 9230</li>
  506. </ul>
  507. <p>For the other services, change the name and port.</p>
  508. <picture><source  
  509. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025webstorm-nodejs-debug-config-dark.png"
  510.        media="(prefers-color-scheme: dark)"
  511.    /><source
  512. srcset="https://akrabat.com/wp-content/uploads/2025/07/2025webstorm-nodejs-debug-config-light.png"
  513.        media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)"
  514.    /><br />
  515.    <img decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025webstorm-nodejs-debug-config-light.png" loading="lazy" alt="Webstorm nodejs debug config light." class="noborder" width="600"/>
  516. </picture>
  517. <p>From the Debugging dropdown at in the title bar select the service and press the green "bug" button. You'll see a "Debugger attached." message in the Docker logs.</p>
  518. <p>Attach a breakpoint and access the endpoint using <tt>curl</tt> or another HTTP client and the IDE should stop execution at the breakpoint.</p>
  519. <h2>Debugging in VS Code</h2>
  520. <p>To set up <a href="https://code.visualstudio.com">VS Code</a> for step debugging, create a <tt>.vscode/launch.json</tt> file in your project. It should look like this:</p>
  521. <pre lang="json">
  522. {
  523.  "version": "0.2.0",
  524.  "configurations": [
  525.    {
  526.      "name": "Debug service1",
  527.      "type": "node",
  528.      "request": "attach",
  529.      "port": 9230,
  530.      "address": "localhost",
  531.      "localRoot": "${workspaceFolder}",
  532.      "remoteRoot": "/usr/src/app",
  533.      "restart": true
  534.    },
  535.    {
  536.      "name": "Debug service2",
  537.      "type": "node",
  538.      "request": "attach",
  539.      "port": 9231,
  540.      "address": "localhost",
  541.      "localRoot": "${workspaceFolder}",
  542.      "remoteRoot": "/usr/src/app",
  543.      "restart": true
  544.    }
  545.  ]
  546. }
  547. </pre>
  548. <p>Set <tt>remoteRoot</tt> to the directory within the Docker container where the project is mounted.</p>
  549. <p>Start debugging by selecting the <em>Run and Debug</em> pane in the left hand toolbar and choose the service from the dropdown at the top. Then press the green <em>Start debugging</em> button (or press F5).You'll see a "Debugger attached." message in the Docker logs.</p>
  550. <p>Attach a breakpoint and access the endpoint using <tt>curl</tt> or another HTTP client and the IDE should stop execution at the breakpoint.</p>
  551. <h2>That's it</h2>
  552. <p>Having done this, I can now enjoy step debugging this new-to-me codebase and understand what it does!</p>
  553. ]]></content:encoded>
  555. <wfw:commentRss>https://akrabat.com/step-debugging-docker-compose-nestjs-services/feed/</wfw:commentRss>
  556. <slash:comments>0</slash:comments>
  559. </item>
  560. <item>
  561. <title>QuickSS: Screenshot the active window on Mac</title>
  562. <link>https://akrabat.com/quickss-screenshot-the-active-window-on-mac/</link>
  563. <comments>https://akrabat.com/quickss-screenshot-the-active-window-on-mac/#respond</comments>
  565. <dc:creator><![CDATA[Rob]]></dc:creator>
  566. <pubDate>Tue, 22 Jul 2025 09:00:00 +0000</pubDate>
  567. <category><![CDATA[Mac]]></category>
  568. <category><![CDATA[Software]]></category>
  569. <guid isPermaLink="false">https://akrabat.com/?p=7418</guid>
  570.  
  571. <description><![CDATA[Back in 2016, I wrote about using QuickGrab to take a screenshot of the active window via a single key press with no mouse use required. It's now 2025 and I'm still using this and Apple has announced that Rosetta 2 will be phased out in a couple of years. As QuickGrab is one of the few Intel-only apps I still use, I thought I'd recompile for Apple Silicon and it was then that I… <a href="https://akrabat.com/quickss-screenshot-the-active-window-on-mac/">continue reading</a>.]]></description>
  572. <content:encoded><![CDATA[<p>Back in 2016, I wrote about using QuickGrab to take a screenshot of the active window via a single key press with no mouse use required.</p>
  573. <p>It's now 2025 and I'm still using this and Apple has announced that Rosetta 2 will be phased out in a couple of years. As QuickGrab is one of the few Intel-only apps I still use, I thought I'd recompile for Apple Silicon and it was then that I ran into trouble:</p>
  574. <pre>
  575. $ gcc -framework cocoa -x objective-c -o quickgrab quickgrab.m
  576. quickgrab.m:92:26: error: 'CGWindowListCreateImage' is unavailable:
  577. obsoleted in macOS 15.0 - Please use ScreenCaptureKit instead.
  578. </pre>
  579. <p><em>Obsoleted in macOS 15.0</em> isn't something you want to see! The APIs that QuickGrab use are no longer part of the SDK and so it cannot be compiled. Hence I decided to replace it with a Swift version and also take the opportunity to add additional features that I wanted.</p>
  580. <p>While on holiday, I wrote <a href="https://github.com/akrabat/QuickSS">QuickSS</a>. I spent some time playing around with ScreenCaptureKit, but couldn't get it to replicate the window shadows that the standard screenshot tool on <tt>shift+cmd+4</tt> does. To solve this I decided to use <tt>screencapture</tt> to take the screenshot which is provided by macOS. </p>
  581. <h2>Screenshot to file</h2>
  582. <p>To save a screenshot of the active window directly to a file, just run <tt>quickss</tt>. You probably want to select cmd+tab to a different window, so prefix with <tt>sleep</tt>:</p>
  583. <pre>
  584. rob@Caledonia QuickGrab (master *) $ sleep 3; quickss
  585. Capturing window ID: 5940 [Safari: 'Rob Allen – Pragmatism in the real world']
  586. Screenshot saved to: /Users/rob/Downloads/Screenshot 2025-07-22 at 11.00.00.png
  587. </pre>
  588. <p>As it's my app, I made some changes to match the way I work with it. Firstly it defaults to saving the file to the Downloads folder and names it the same as the default screenshot utility. You can use <tt>--file</tt> to override this should you need to and <tt>--quiet</tt> will output just the filename which is useful for onward scripting, or displaying in notifications.</p>
  589. <h2>Screenshot directly to clipboard</h2>
  590. <p>I also added the ability to put the screenshot directly onto the clipboard with <tt>--clipboard</tt></p>
  591. <pre>
  592. $ sleep 3; quickss --clipboard
  593. Capturing window ID: 5940 [Safari: 'Rob Allen – Pragmatism in the real world']
  594. Screenshot copied to clipboard
  595. </pre>
  596. <p>I can now paste directly into Slack/Discord/Messages/Messenger/WhatsApp/Signal/etc. (Yes, there are far too many of these services nowadays!)</p>
  597. <h2>Keyboard shortcut</h2>
  598. <p>Obviously, the best way to run this is to use global keyboard shortcuts. My preference is to use <tt style="font-family: sans-serif">⌃⌥⌘4</tt> to put the screenshot onto the clipboard and <tt style="font-family: sans-serif">⇧⌃⌥⌘4</tt> to save it to file.</p>
  599. <h3>Using Shortcuts.app</h3>
  600. <p>You can use the Shortcuts app for this and create a shortcut for copying to clipboard like this:</p>
  601. <p><img decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025quickss-take-screenshot-to-cliboard.png" alt="Quickss take screenshot to cliboard." title="quickss-take-screenshot-to-cliboard.png" border="0" width="700" height="511" /></p>
  602. <p>The equivalent for saving to file is the same, except that you don't need the <tt>--clipboard</tt> parameter.</p>
  603. <h3>Using Alfred</h3>
  604. <p>I use <a href="https://www.alfredapp.com/">Alfred</a> for these sort of things, so I wrote a Workflow to do this based on the previous one:</p>
  605. <p><img loading="lazy" decoding="async" src="https://akrabat.com/wp-content/uploads/2025/07/2025quickss-alfred-workflow.png" alt="Quickss alfred workflow." title="quickss-alfred-workflow.png" border="0" width="700" height="363" /></p>
  606. <p>It's downloadable from the <a href="https://github.com/akrabat/QuickSS/releases/latest">QuickSS latest release</a> page.</p>
  607. <h2>That's it</h2>
  608. <p>Over the years, I've found that having a global hotkey to screenshot the current active window is really helpful. I like it even more now that it goes directly to the clipboard.</p>
  609. ]]></content:encoded>
  611. <wfw:commentRss>https://akrabat.com/quickss-screenshot-the-active-window-on-mac/feed/</wfw:commentRss>
  612. <slash:comments>0</slash:comments>
  615. </item>
  616. <item>
  617. <title>Notarising a macOS standalone binary</title>
  618. <link>https://akrabat.com/notarising-a-macos-standalone-binary/</link>
  619. <comments>https://akrabat.com/notarising-a-macos-standalone-binary/#respond</comments>
  621. <dc:creator><![CDATA[Rob]]></dc:creator>
  622. <pubDate>Tue, 15 Jul 2025 09:00:00 +0000</pubDate>
  623. <category><![CDATA[Command Line]]></category>
  624. <category><![CDATA[Development]]></category>
  625. <category><![CDATA[Shell Scripting]]></category>
  626. <guid isPermaLink="false">https://akrabat.com/?p=7413</guid>
  627.  
  628. <description><![CDATA[I've been writing a simple Swift command line tool called QuickSS. It's a single file swift file, that I compile to a standalone binaryusing: swiftc quickss.swift -o quickss To distribute it on modern Macs, I need to sign it and then get Apple to notarise it. Signing the binary To sign the binary, you need a "Developer ID Application" certificate from your paid developer account. If you don't have one there already create a new… <a href="https://akrabat.com/notarising-a-macos-standalone-binary/">continue reading</a>.]]></description>
  629. <content:encoded><![CDATA[<p>I've been writing a simple Swift command line tool called QuickSS. It's a single file swift file, that I compile to a standalone binaryusing:</p>
  630. <pre>
  631. swiftc quickss.swift -o quickss
  632. </pre>
  633. <p>To distribute it on modern Macs, I need to sign it and then get Apple to notarise it.</p>
  634. <h2>Signing the binary</h2>
  635. <p>To sign the binary, you need a "Developer ID Application" certificate from your paid <a href="https://developer.apple.com/account/resources/certificates/list">developer account</a>. If you don't have one there already create a new one, which requires a CSR from Keychain. Fortunately, the <a href="https://developer.apple.com/help/account/certificates/create-a-certificate-signing-request">info on what to do</a> is clear.</p>
  636. <p>Download your Developer ID Application certificate and add to Keychain Access.</p>
  637. <p>Next you need its name. This is done using <tt>security find-identity -v -p codesigning</tt> which gives you a list of certs. You want the text between the <tt>"</tt> that starts "Developer ID Application:". The easiest way to get this if you are scripting it is:</p>
  638. <pre>
  639. IDENTITY=$(security find-identity -v -p codesigning | grep "Developer ID Application" | grep -m 1 -oE '"[^"]+"' | tr -d '"')
  640. </pre>
  641. <p>To actually sign the binary, use the <tt>codesign</tt> utility:</p>
  642. <pre>
  643. codesign --timestamp --options runtime --sign "$IDENTITY" quickss
  644. </pre>
  645. <h2>Notarising</h2>
  646. <p>To notarise the binary, you use the <tt>notarytool</tt> utility within <tt>xcrun</tt>. This expects a zip or pkg file, so zip up the binary first. You also need to know your Apple developer account's Team ID, your Apple ID and you need an app-specific password from <a href="https://account.apple.com">account.apple.com</a>.</p>
  647. <p>Submit your app for notarising with:</p>
  648. <pre>
  649. zip -q quickss.zip quickss
  650.  
  651. xcrun notarytool submit  --wait --no-progress -f json \
  652.    --team-id "$TEAM_ID" \
  653.    --apple-id "$APPLE_ID" \
  654.    --password "$APP_SPECIFIC_PASSWORD" \
  655.    quickss.zip
  656.  
  657. rm quickss.zip
  658. </pre>
  659. <p>If it fails, use the submission ID to query the log:</p>
  660. <pre>
  661. xcrun notarytool log \
  662.    --team-id "$TEAM_ID" \
  663.    --apple-id "$APPLE_ID" \
  664.    --password "$APP_SPECIFIC_PASSWORD" \
  665.    "&lt;submission ID&gt;"
  666. </pre>
  667. <p>Apple has now notarised your app.</p>
  668. <h2>Note: No need to staple</h2>
  669. <p>For a standard Mac applications (<tt>.app</tt> bundles), you can "staple" the notarisation into it. This makes things more efficient for the GateKeeper technology. However, for a standalone binary, <em>this cannot be done</em> as there is no directory into which to store the notarisation file.</p>
  670. <p>If you try to staple, you'll get <tt>The staple and validate action failed! Error 73</tt> with no further information which is not entirely helpful.</p>
  671. <p>For standalone binaries GateKeeper checks directly with Apple's servers the first time they are run, so stapling is unnecessary.</p>
  672. <h2>That's it</h2>
  673. <p>That's it. You now have a notarised standalone binary that can be easily distributed.</p>
  674. ]]></content:encoded>
  676. <wfw:commentRss>https://akrabat.com/notarising-a-macos-standalone-binary/feed/</wfw:commentRss>
  677. <slash:comments>0</slash:comments>
  680. </item>
  681. <item>
  682. <title>Using the 1Password CLI in a script</title>
  683. <link>https://akrabat.com/using-the-1password-cli-in-a-script/</link>
  684. <comments>https://akrabat.com/using-the-1password-cli-in-a-script/#respond</comments>
  686. <dc:creator><![CDATA[Rob]]></dc:creator>
  687. <pubDate>Tue, 08 Jul 2025 09:00:00 +0000</pubDate>
  688. <category><![CDATA[Command Line]]></category>
  689. <category><![CDATA[Development]]></category>
  690. <category><![CDATA[Shell Scripting]]></category>
  691. <guid isPermaLink="false">https://akrabat.com/?p=7407</guid>
  692.  
  693. <description><![CDATA[I'm currently writing a script that notarises a macOS CLI app which needs to access a password. Rather than put it in an environment variable, I thought I'd use the 1Password CLI. This is the first time I've used it, so these are my notes. The 1Password CLI tool is call op. I installed it via Homebrew with: brew install 1password-cli Sign in You need to sign in. op signin As I have multiple accounts… <a href="https://akrabat.com/using-the-1password-cli-in-a-script/">continue reading</a>.]]></description>
  694. <content:encoded><![CDATA[<p>I'm currently writing a script that notarises a macOS CLI app which needs to access a password. Rather than put it in an environment variable, I thought I'd use the 1Password CLI. This is the first time I've used it, so these are my notes.</p>
  695. <p>The 1Password CLI tool is call <tt>op</tt>. I installed it via Homebrew with:</p>
  696. <pre>brew install 1password-cli</pre>
  697. <h2>Sign in</h2>
  698. <p>You need to sign in. </p>
  699. <pre>op signin</pre>
  700. <p>As I have multiple accounts as various clients have shared access to specific vaults, it asks me which account I want to sign in. To save this step, you can set the <tt>OP_ACCOUNT</tt> environment variable:</p>
  701. <pre>export OP_ACCOUNT=my.1password.com</pre>
  702. <p>Alternatively, use the <tt>--account</tt> parameter.</p>
  703. <p>You get a dialog box where for me, I use TouchID to sign in.</p>
  704. <p><tt>op signin</tt> is idempotent so is a no-op if the Terminal is already signed in.</p>
  705. <h2>Access data</h2>
  706. <p>There are multiple ways to retrieve the data from a 1Password item.</p>
  707. <h3><tt style="color:inherit">op item get</tt></h3>
  708. <p>Use <tt>op item get "&lt;item&gt;" --field "&lt;fieldname&gt;"</tt> to get a specific field. e.g</p>
  709. <pre>op item get "Apple App Notarisation" --field "username"</pre>
  710. <p>The <tt>&lt;item&gt;</tt> can be the name of the item or its id. e.g. something like <tt>dajka2z5l57m4p43s6bapd3eo4</tt></p>
  711. <p>Note, that for a password, you also need to pass in <tt>--reveal</tt>.</p>
  712. <p>As I'm writing a script, I assign to a variable:</p>
  713. <pre>
  714. APPLE_ID=$(op item get "Apple App Notarisation" --field username)
  715. APP_SPECIFIC_PASSWORD=$(op item get "Apple App Notarisation" --field password --reveal)
  716. TEAM_ID=$(op item get "Apple App Notarisation" --field team_id)
  717. </pre>
  718. <p>Alternatively, you can get back multiple fields in one go by providing a list of comma separated fields:</p>
  719. <pre>
  720. FIELDS=$(op item get "Apple App Notarisation" --fields username,password,team_id --reveal)
  721. IFS=',' read -r APPLE_ID APP_SPECIFIC_PASSWORD TEAM_ID <<< "$FIELDS"
  722. </pre>
  723. <h3><tt style="color:inherit">op read</tt></h3>
  724. <p>You can also use the <tt>read parameter</tt> which takes a URL-style path:</p>
  725. <pre>
  726. op read op://&lt;vault&gt;/&lt;item&gt;/&lt;field&gt;
  727. </pre>
  728. <p>Use <tt>op vault list</tt> to view the list of vault names and you don't need <tt>--reveal</tt> for passwords. </p>
  729. <p>For my case, I can use:</p>
  730. <pre>
  731. APPLE_ID=$(read "op://Private/Apple App Notarisation/username")
  732. APP_SPECIFIC_PASSWORD=$(op read "op://Private/Apple App Notarisation/password")
  733. TEAM_ID=$(op read "op://Private/Apple App Notarisation/team_id")
  734. </pre>
  735. <h3>Format as JSON</h3>
  736. <p>You can also get the entire item in JSON using:</p>
  737. <pre>op item get "Apple App Notarisation" --format json</pre>
  738. <p>Then use <a href="https://jqlang.org/"><tt>jq</tt></a> to extract what you need. e.g to print the username and password you could do:</p>
  739. <pre>op item get "Apple App Notarisation" --format json | jq -r '
  740.  .fields[] | select(.label=="username" or .label=="password") | "\(.label): \(.value)"
  741. '</pre>
  742. <h3>That's it</h3>
  743. <p>That's it. Very simple to put into a script and keep my password secure.</p>
  744. ]]></content:encoded>
  746. <wfw:commentRss>https://akrabat.com/using-the-1password-cli-in-a-script/feed/</wfw:commentRss>
  747. <slash:comments>0</slash:comments>
  750. </item>
  751. </channel>
  752. </rss>
  753.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//akrabat.com/feed/

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda