100 lines
No EOL
3.6 KiB
JSON
100 lines
No EOL
3.6 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "56df3f74-7cd2-4229-98b7-a593d435ad70"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-05-11T09:00:16+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": "Switching web servers using Build Configs"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-04-03T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:16+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/04\/03\/switching-web-servers-using-build-configs",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Have you been in a situation where you needed to switch something in a project, like the type of database or a payment provider?<\/p>\n\n<p>Today, I decided to switch a project from NGINX to Apache.<\/p>\n\n<p>Usually, this would involve using a different base Docker image, creating new configuration files, and changing things like the root directory for my project.<\/p>\n\n<p>But, because I'd built this into <a href=\"https:\/\/www.oliverdavies.uk\/talks\/building-build-configs\">Build Configs<\/a>, I was able to change a few lines in one file, and when I re-generated the configuration files, this project was running Apache.<\/p>\n\n<p>This is an excellent example of why I built this tool: to save time and reduce duplication across my projects.<\/p>\n\n<p>For this change, it did both.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Have you been in a situation where you needed to switch something in a project, like the type of database or a payment provider?<\/p>\n\n<p>Today, I decided to switch a project from NGINX to Apache.<\/p>\n\n<p>Usually, this would involve using a different base Docker image, creating new configuration files, and changing things like the root directory for my project.<\/p>\n\n<p>But, because I'd built this into <a href=\"https:\/\/www.oliverdavies.uk\/talks\/building-build-configs\">Build Configs<\/a>, I was able to change a few lines in one file, and when I re-generated the configuration files, this project was running Apache.<\/p>\n\n<p>This is an excellent example of why I built this tool: to save time and reduce duplication across my projects.<\/p>\n\n<p>For this change, it did both.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-05-11T09:00:16+00:00",
|
|
"guid": null,
|
|
"hash": "df8a1f8e4c5825078db0d4b92837624d",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |