tome export

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

View file

@ -82,15 +82,15 @@
],
"body": [
{
"value": "\n <p>How do you update your environments?<\/p>\n\n<p>I've done it in two different ways on different projects.<\/p>\n\n<p>The most common way is to download a database from another environment and import it.<\/p>\n\n<p>The downside is that there needs to be a blessed database for everyone to use and someone needs to maintain and update.<\/p>\n\n<p>It can also contain user data, such as usernames, email addresses, passwords and webform submissions that you should sanitise or remove.<\/p>\n\n<p>The other option is to install the application from scratch.<\/p>\n\n<p>For Drupal projects, this means installing using the existing configuration to re-create the content types, fields, views, block types, etc.<\/p>\n\n<p>This confirms the configuration is installable or it will fail.<\/p>\n\n<p>As it's a fresh installation, it can be run by anyone without needing to maintain an blessed database and doesn't contain any user data.<\/p>\n\n<p>Then you can recreate any data, such as users or content, that you need or seed the database with standard data.<\/p>\n\n<p>For Drupal, <a href=\"/daily\/2024\/09\/16\/experimenting-with-the-default-content-module\">I've been using the Default Content module<\/a> for this, which has been working very well.<\/p>\n\n<p>If I can, I much prefer the install approach rather than importing.<\/p>\n\n<p>Which do you do, or do you do something else?<\/p>\n\n ",
"value": "\n <p>How do you update your environments?<\/p>\n\n<p>I've done it in two different ways on different projects.<\/p>\n\n<p>The most common way is to download a database from another environment and import it.<\/p>\n\n<p>The downside is that there needs to be a blessed database for everyone to use and someone needs to maintain and update.<\/p>\n\n<p>It can also contain user data, such as usernames, email addresses, passwords and webform submissions that you should sanitise or remove.<\/p>\n\n<p>The other option is to install the application from scratch.<\/p>\n\n<p>For Drupal projects, this means installing using the existing configuration to re-create the content types, fields, views, block types, etc.<\/p>\n\n<p>This confirms the configuration is installable or it will fail.<\/p>\n\n<p>As it's a fresh installation, it can be run by anyone without needing to maintain an blessed database and doesn't contain any user data.<\/p>\n\n<p>Then you can recreate any data, such as users or content, that you need or seed the database with standard data.<\/p>\n\n<p>For Drupal, <a href=\"\/daily\/2024\/09\/16\/experimenting-with-the-default-content-module\">I've been using the Default Content module<\/a> for this, which has been working very well.<\/p>\n\n<p>If I can, I much prefer the install approach rather than importing.<\/p>\n\n<p>Which do you do, or do you do something else?<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>How do you update your environments?<\/p>\n\n<p>I've done it in two different ways on different projects.<\/p>\n\n<p>The most common way is to download a database from another environment and import it.<\/p>\n\n<p>The downside is that there needs to be a blessed database for everyone to use and someone needs to maintain and update.<\/p>\n\n<p>It can also contain user data, such as usernames, email addresses, passwords and webform submissions that you should sanitise or remove.<\/p>\n\n<p>The other option is to install the application from scratch.<\/p>\n\n<p>For Drupal projects, this means installing using the existing configuration to re-create the content types, fields, views, block types, etc.<\/p>\n\n<p>This confirms the configuration is installable or it will fail.<\/p>\n\n<p>As it's a fresh installation, it can be run by anyone without needing to maintain an blessed database and doesn't contain any user data.<\/p>\n\n<p>Then you can recreate any data, such as users or content, that you need or seed the database with standard data.<\/p>\n\n<p>For Drupal, <a href=\"/daily\/2024\/09\/16\/experimenting-with-the-default-content-module\">I've been using the Default Content module<\/a> for this, which has been working very well.<\/p>\n\n<p>If I can, I much prefer the install approach rather than importing.<\/p>\n\n<p>Which do you do, or do you do something else?<\/p>\n\n ",
"processed": "\n <p>How do you update your environments?<\/p>\n\n<p>I've done it in two different ways on different projects.<\/p>\n\n<p>The most common way is to download a database from another environment and import it.<\/p>\n\n<p>The downside is that there needs to be a blessed database for everyone to use and someone needs to maintain and update.<\/p>\n\n<p>It can also contain user data, such as usernames, email addresses, passwords and webform submissions that you should sanitise or remove.<\/p>\n\n<p>The other option is to install the application from scratch.<\/p>\n\n<p>For Drupal projects, this means installing using the existing configuration to re-create the content types, fields, views, block types, etc.<\/p>\n\n<p>This confirms the configuration is installable or it will fail.<\/p>\n\n<p>As it's a fresh installation, it can be run by anyone without needing to maintain an blessed database and doesn't contain any user data.<\/p>\n\n<p>Then you can recreate any data, such as users or content, that you need or seed the database with standard data.<\/p>\n\n<p>For Drupal, <a href=\"http:\/\/default\/daily\/2024\/09\/16\/experimenting-with-the-default-content-module\">I've been using the Default Content module<\/a> for this, which has been working very well.<\/p>\n\n<p>If I can, I much prefer the install approach rather than importing.<\/p>\n\n<p>Which do you do, or do you do something else?<\/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": "e320d92eee616c932a9a3fe26b35047c",
"target_type": "feeds_feed",