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.d047a824-fbb1-40b0-8391-ceba0cc250f5.json
View file

@ -82,15 +82,15 @@
],
"body": [
{
"value": "\n <p><a href=\"/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">One of my earliest daily emails was about <code>run<\/code> files<\/a> - files that contain Bash functions that combine or simplify project-specific tasks.<\/p>\n\n<p>In Drupal projects, these could be to execute Composer or Drush commands, connect to the database, or run automated tests.<\/p>\n\n<p>For my CI pipelines, I like to use a function called <code>ci:test<\/code> that contains all the commands to run in the pipeline.<\/p>\n\n<p>This keeps the pipeline configuration as simple and agnostic as possible.<\/p>\n\n<p>It also makes it easy for people to read and, because it's a bash file, it will run anywhere without any additional tools.<\/p>\n\n<p>For an example, <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\/blob\/d18bf2242fba1291cabf1e16a5badb6fda7ce509\/run#L16-L35\">see my Drupal Docker example repository<\/a>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The main advantage, though, is being able to run the pipeline locally, if you need to.<\/p>\n\n<p>Maybe you need to debug a failure in the pipeline or you want to test a change to the pipeline locally before pushing it.<\/p>\n\n<p>By using a command in a <code>run<\/code> file, doing so is as simple as running that one command.<\/p>\n\n ",
"value": "\n <p><a href=\"\/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">One of my earliest daily emails was about <code>run<\/code> files<\/a> - files that contain Bash functions that combine or simplify project-specific tasks.<\/p>\n\n<p>In Drupal projects, these could be to execute Composer or Drush commands, connect to the database, or run automated tests.<\/p>\n\n<p>For my CI pipelines, I like to use a function called <code>ci:test<\/code> that contains all the commands to run in the pipeline.<\/p>\n\n<p>This keeps the pipeline configuration as simple and agnostic as possible.<\/p>\n\n<p>It also makes it easy for people to read and, because it's a bash file, it will run anywhere without any additional tools.<\/p>\n\n<p>For an example, <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\/blob\/d18bf2242fba1291cabf1e16a5badb6fda7ce509\/run#L16-L35\">see my Drupal Docker example repository<\/a>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The main advantage, though, is being able to run the pipeline locally, if you need to.<\/p>\n\n<p>Maybe you need to debug a failure in the pipeline or you want to test a change to the pipeline locally before pushing it.<\/p>\n\n<p>By using a command in a <code>run<\/code> file, doing so is as simple as running that one command.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p><a href=\"/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">One of my earliest daily emails was about <code>run<\/code> files<\/a> - files that contain Bash functions that combine or simplify project-specific tasks.<\/p>\n\n<p>In Drupal projects, these could be to execute Composer or Drush commands, connect to the database, or run automated tests.<\/p>\n\n<p>For my CI pipelines, I like to use a function called <code>ci:test<\/code> that contains all the commands to run in the pipeline.<\/p>\n\n<p>This keeps the pipeline configuration as simple and agnostic as possible.<\/p>\n\n<p>It also makes it easy for people to read and, because it's a bash file, it will run anywhere without any additional tools.<\/p>\n\n<p>For an example, <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\/blob\/d18bf2242fba1291cabf1e16a5badb6fda7ce509\/run#L16-L35\">see my Drupal Docker example repository<\/a>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The main advantage, though, is being able to run the pipeline locally, if you need to.<\/p>\n\n<p>Maybe you need to debug a failure in the pipeline or you want to test a change to the pipeline locally before pushing it.<\/p>\n\n<p>By using a command in a <code>run<\/code> file, doing so is as simple as running that one command.<\/p>\n\n ",
"processed": "\n <p><a href=\"http:\/\/default\/daily\/2022\/08\/15\/using-run-file-simplify-project-tasks\">One of my earliest daily emails was about <code>run<\/code> files<\/a> - files that contain Bash functions that combine or simplify project-specific tasks.<\/p>\n\n<p>In Drupal projects, these could be to execute Composer or Drush commands, connect to the database, or run automated tests.<\/p>\n\n<p>For my CI pipelines, I like to use a function called <code>ci:test<\/code> that contains all the commands to run in the pipeline.<\/p>\n\n<p>This keeps the pipeline configuration as simple and agnostic as possible.<\/p>\n\n<p>It also makes it easy for people to read and, because it's a bash file, it will run anywhere without any additional tools.<\/p>\n\n<p>For an example, <a href=\"https:\/\/github.com\/opdavies\/docker-example-drupal\/blob\/d18bf2242fba1291cabf1e16a5badb6fda7ce509\/run#L16-L35\">see my Drupal Docker example repository<\/a>.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>The main advantage, though, is being able to run the pipeline locally, if you need to.<\/p>\n\n<p>Maybe you need to debug a failure in the pipeline or you want to test a change to the pipeline locally before pushing it.<\/p>\n\n<p>By using a command in a <code>run<\/code> file, doing so is as simple as running that one command.<\/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": "3e61ae665c2eec6ae6c753e53475f4eb",
"target_type": "feeds_feed",