100 lines
No EOL
4.1 KiB
JSON
100 lines
No EOL
4.1 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "1bbeeb87-afe3-41ff-a682-b3dcdffb349f"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-16T14:12:56+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": "Static websites are easy to host and deploy"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2025-03-13T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-16T14:12:56+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2025\/03\/13\/deploy",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>Another reason I like static websites is that they're easy and quick to deploy.<\/p>\n\n<p>Whether you use write each HTML file by hand or <a href=\"http:\/\/localhost:8000\/daily\/2025\/03\/12\/easy\">use a static site generator<\/a>, a simple Web server like Caddy, Nginx or Apache can load and serve your website for everyone to see.<\/p>\n\n<p>My Sculpin website generates an output_prod directory after I run <code>sculpin generate<\/code> with my deployable files.<\/p>\n\n<p>I manage my own server with NixOS that hosts a number of static websites, such as examples from talks and blog posts.<\/p>\n\n<p>To upload my files onto the server, I just use rsync - a small command line tool to synchronise files between computers.<\/p>\n\n<p>It's a single command to upload the contents of my output_prod directory to the directory on my server.<\/p>\n\n<p>No complex CI pipelines or database migrations.<\/p>\n\n<p>It's fast, simple and minimal.<\/p>\n\n<p>If you prefer to use a service like Netlify or Vercel, they work great for static websites too.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>Another reason I like static websites is that they're easy and quick to deploy.<\/p>\n\n<p>Whether you use write each HTML file by hand or <a href=\"http:\/\/localhost:8000\/daily\/2025\/03\/12\/easy\">use a static site generator<\/a>, a simple Web server like Caddy, Nginx or Apache can load and serve your website for everyone to see.<\/p>\n\n<p>My Sculpin website generates an output_prod directory after I run <code>sculpin generate<\/code> with my deployable files.<\/p>\n\n<p>I manage my own server with NixOS that hosts a number of static websites, such as examples from talks and blog posts.<\/p>\n\n<p>To upload my files onto the server, I just use rsync - a small command line tool to synchronise files between computers.<\/p>\n\n<p>It's a single command to upload the contents of my output_prod directory to the directory on my server.<\/p>\n\n<p>No complex CI pipelines or database migrations.<\/p>\n\n<p>It's fast, simple and minimal.<\/p>\n\n<p>If you prefer to use a service like Netlify or Vercel, they work great for static websites too.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-16T14:12:56+00:00",
|
|
"guid": null,
|
|
"hash": "93714084df9893992c84f56a745f4bb2",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |