opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

tome export

Browse source
This commit is contained in:
Oliver Davies 2025-05-30 02:14:32 +01:00
parent 52278c3a53
commit 7a52afab5f
960 changed files with 3670 additions and 2229 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/node.f2220fec-35de-40a7-be72-9b3b643e15df.json
View file

@ -82,15 +82,15 @@
],
"body": [
{
"value": "\n <p><a href=\"/daily\/2025\/01\/19\/minimum-viable-development-environment\">In yesterday's email<\/a>, I showed how I've been using Nix and flake files to build reproducible and shareable development environments for Drupal applications.<\/p>\n\n<p>The reason it's reproducible is the <code>flake.lock<\/code> file.<\/p>\n\n<p>Similar to <code>composer.lock<\/code> or <code>package-lock.json<\/code>, it captures the exact versions of the packages installed from the nixpkgs repository.<\/p>\n\n<p>This file, along with <code>flake.nix<\/code>, can be committed alongside the application code and anyone with Nix installed can run <code>nix develop<\/code> to get a shell with the same packages and dependencies.<\/p>\n\n<p>This isn't the same as other solutions, where you add something like <code>FROM php:8.2<\/code> but, because there's no lockfile, there's no guarantee the same package versions will be installed so there could be mismatches that cause errors.<\/p>\n\n<p>With <code>flake.lock<\/code>, the environment isn't just repeatable - it's completely reproducible.<\/p>\n\n<p>Locally, in a CI pipeline or in production.<\/p>\n\n ",
"value": "\n <p><a href=\"\/daily\/2025\/01\/19\/minimum-viable-development-environment\">In yesterday's email<\/a>, I showed how I've been using Nix and flake files to build reproducible and shareable development environments for Drupal applications.<\/p>\n\n<p>The reason it's reproducible is the <code>flake.lock<\/code> file.<\/p>\n\n<p>Similar to <code>composer.lock<\/code> or <code>package-lock.json<\/code>, it captures the exact versions of the packages installed from the nixpkgs repository.<\/p>\n\n<p>This file, along with <code>flake.nix<\/code>, can be committed alongside the application code and anyone with Nix installed can run <code>nix develop<\/code> to get a shell with the same packages and dependencies.<\/p>\n\n<p>This isn't the same as other solutions, where you add something like <code>FROM php:8.2<\/code> but, because there's no lockfile, there's no guarantee the same package versions will be installed so there could be mismatches that cause errors.<\/p>\n\n<p>With <code>flake.lock<\/code>, the environment isn't just repeatable - it's completely reproducible.<\/p>\n\n<p>Locally, in a CI pipeline or in production.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p><a href=\"/daily\/2025\/01\/19\/minimum-viable-development-environment\">In yesterday's email<\/a>, I showed how I've been using Nix and flake files to build reproducible and shareable development environments for Drupal applications.<\/p>\n\n<p>The reason it's reproducible is the <code>flake.lock<\/code> file.<\/p>\n\n<p>Similar to <code>composer.lock<\/code> or <code>package-lock.json<\/code>, it captures the exact versions of the packages installed from the nixpkgs repository.<\/p>\n\n<p>This file, along with <code>flake.nix<\/code>, can be committed alongside the application code and anyone with Nix installed can run <code>nix develop<\/code> to get a shell with the same packages and dependencies.<\/p>\n\n<p>This isn't the same as other solutions, where you add something like <code>FROM php:8.2<\/code> but, because there's no lockfile, there's no guarantee the same package versions will be installed so there could be mismatches that cause errors.<\/p>\n\n<p>With <code>flake.lock<\/code>, the environment isn't just repeatable - it's completely reproducible.<\/p>\n\n<p>Locally, in a CI pipeline or in production.<\/p>\n\n ",
"processed": "\n <p><a href=\"http:\/\/default\/daily\/2025\/01\/19\/minimum-viable-development-environment\">In yesterday's email<\/a>, I showed how I've been using Nix and flake files to build reproducible and shareable development environments for Drupal applications.<\/p>\n\n<p>The reason it's reproducible is the <code>flake.lock<\/code> file.<\/p>\n\n<p>Similar to <code>composer.lock<\/code> or <code>package-lock.json<\/code>, it captures the exact versions of the packages installed from the nixpkgs repository.<\/p>\n\n<p>This file, along with <code>flake.nix<\/code>, can be committed alongside the application code and anyone with Nix installed can run <code>nix develop<\/code> to get a shell with the same packages and dependencies.<\/p>\n\n<p>This isn't the same as other solutions, where you add something like <code>FROM php:8.2<\/code> but, because there's no lockfile, there's no guarantee the same package versions will be installed so there could be mismatches that cause errors.<\/p>\n\n<p>With <code>flake.lock<\/code>, the environment isn't just repeatable - it's completely reproducible.<\/p>\n\n<p>Locally, in a CI pipeline or in production.<\/p>\n\n ",
"summary": null
}
],
"feeds_item": [
{
"imported": "1970-01-01T00:33:45+00:00",
"imported": "1970-01-01T00:32:50+00:00",
"guid": null,
"hash": "53ca25f2417162597931bed0d3c8cb57",
"target_type": "feeds_feed",