Oliver Davies
7a7dc297ca
Now the abs_to_rel module is enabled, links can be made relative so they work on the current environment.
100 lines
No EOL
5.5 KiB
JSON
100 lines
No EOL
5.5 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "7210b16f-71c2-44c4-9dc1-4264b243c618"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-05-11T08:59:58+00:00"
|
|
}
|
|
],
|
|
"revision_uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"revision_log": [],
|
|
"status": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"title": [
|
|
{
|
|
"value": "Chaining tools for maximum benefit"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2025-04-08T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T08:59:58+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2025\/04\/08\/chaining",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Yesterday I showed <a href=\"/daily\/2025\/04\/07\/nix-rst2pdf\">how I'm using Nix to build my presentation slide decks<\/a> with rst2pdf.<\/p>\n\n<p>This allows me to run a simple command like <code>nix build .#test-driven-drupal<\/code> to build the slides for the given presentation.<\/p>\n\n<p>But I can use other tools to make this even easier.<\/p>\n\n<p>What if I wanted to have a list of the available presentations to select from, and selecting one would build it?<\/p>\n\n<p>Following the UNIX philosophy, I can use multiple tools together to achieve this.<\/p>\n\n<p>Firstly, I can run <code>nix flake show --json<\/code> to show the output from my flake.nix file, which looks something like this:<\/p>\n\n<pre><code class=\"json\">{\n \"devShells\": { ... },\n \"formatter\": { ... },\n \"packages\": {\n \"x86_64-linux\": {\n \"build-configs\": { ... },\n \"sculpin\": { ... },\n \"shared\": { ... }\n }\n }\n}\n<\/code><\/pre>\n\n<p>The package names - a.k.a. the presentation names - are what I want to select from.<\/p>\n\n<p>I can parse the JSON object with <code>jq<\/code>, remove any unwanted options with <code>grep -v<\/code> and use <code>fzf<\/code> to give me a list I can fuzzy search in.<\/p>\n\n<p>In a Bash script, I can assign this to a variable:<\/p>\n\n<pre><code class=\"bash\">selected=$(nix flake show --json | jq --raw-output '.packages[\"x86_64-linux\"] | keys[]' | grep -v shared | fzf)\n<\/code><\/pre>\n\n<p>Once I have selected a name, I can call <code>nix build<\/code> on it.<\/p>\n\n<pre><code class=\"bash\">nix build .#\"$selected\"\n<\/code><\/pre>\n\n<p>This is a simple example, but it shows how programs can be used together and output can be passed through each program to get the result you want.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Yesterday I showed <a href=\"/daily\/2025\/04\/07\/nix-rst2pdf\">how I'm using Nix to build my presentation slide decks<\/a> with rst2pdf.<\/p>\n\n<p>This allows me to run a simple command like <code>nix build .#test-driven-drupal<\/code> to build the slides for the given presentation.<\/p>\n\n<p>But I can use other tools to make this even easier.<\/p>\n\n<p>What if I wanted to have a list of the available presentations to select from, and selecting one would build it?<\/p>\n\n<p>Following the UNIX philosophy, I can use multiple tools together to achieve this.<\/p>\n\n<p>Firstly, I can run <code>nix flake show --json<\/code> to show the output from my flake.nix file, which looks something like this:<\/p>\n\n<pre><code class=\"json\">{\n \"devShells\": { ... },\n \"formatter\": { ... },\n \"packages\": {\n \"x86_64-linux\": {\n \"build-configs\": { ... },\n \"sculpin\": { ... },\n \"shared\": { ... }\n }\n }\n}\n<\/code><\/pre>\n\n<p>The package names - a.k.a. the presentation names - are what I want to select from.<\/p>\n\n<p>I can parse the JSON object with <code>jq<\/code>, remove any unwanted options with <code>grep -v<\/code> and use <code>fzf<\/code> to give me a list I can fuzzy search in.<\/p>\n\n<p>In a Bash script, I can assign this to a variable:<\/p>\n\n<pre><code class=\"bash\">selected=$(nix flake show --json | jq --raw-output '.packages[\"x86_64-linux\"] | keys[]' | grep -v shared | fzf)\n<\/code><\/pre>\n\n<p>Once I have selected a name, I can call <code>nix build<\/code> on it.<\/p>\n\n<pre><code class=\"bash\">nix build .#\"$selected\"\n<\/code><\/pre>\n\n<p>This is a simple example, but it shows how programs can be used together and output can be passed through each program to get the result you want.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "1970-01-01T00:33:45+00:00",
|
|
"guid": null,
|
|
"hash": "6a6105cc8b6ef3e9fadb5aec0f56aaeb",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |