91 lines
No EOL
3.9 KiB
JSON
91 lines
No EOL
3.9 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "26f6be13-6309-441d-977f-eb84684b8a2f"
|
|
}
|
|
],
|
|
"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:03+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": "The more differences there are, the more likely there will be bugs"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-12-26T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-05-11T09:00:03+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/12\/26\/differences",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>The <a href=\"\/daily\/2024\/12\/24\/moving-changes\">harder it is to update an environment<\/a>, the less often it will be done and the more out of sync your environments will become.<\/p>\n\n<p>The more out of sync your environments are, the higher the chance there will be bugs or issues when changes are moved between environments.<\/p>\n\n<p>I've had situations where the code I wrote worked for my local database but didn't when moved to staging or production.<\/p>\n\n<p>I worked at one company where my development database was refreshed nightly, so my site was at most one day out of sync with production.<\/p>\n\n<p>I knew my code would work with the latest production data and not only the data from days, weeks or months before.<\/p>\n\n<p>It also meant that I needed to write my changes in an automated and repeatable way so they would be executed on the refreshed database and re-added instead of having to do it manually.<\/p>\n\n<p>How in sync are your environments and how similar to production is the environment you're testing against?<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>The <a href=\"http:\/\/default\/daily\/2024\/12\/24\/moving-changes\">harder it is to update an environment<\/a>, the less often it will be done and the more out of sync your environments will become.<\/p>\n\n<p>The more out of sync your environments are, the higher the chance there will be bugs or issues when changes are moved between environments.<\/p>\n\n<p>I've had situations where the code I wrote worked for my local database but didn't when moved to staging or production.<\/p>\n\n<p>I worked at one company where my development database was refreshed nightly, so my site was at most one day out of sync with production.<\/p>\n\n<p>I knew my code would work with the latest production data and not only the data from days, weeks or months before.<\/p>\n\n<p>It also meant that I needed to write my changes in an automated and repeatable way so they would be executed on the refreshed database and re-added instead of having to do it manually.<\/p>\n\n<p>How in sync are your environments and how similar to production is the environment you're testing against?<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
]
|
|
} |