Now the abs_to_rel module is enabled, links can be made relative so they work on the current environment.
100 lines
No EOL
4.1 KiB
JSON
100 lines
No EOL
4.1 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "987bb32d-4dc3-49ff-bc30-2563ea769769"
|
|
}
|
|
],
|
|
"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": "Enjoying a cup of Gitea"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-12-13T00: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\/13\/gitea",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>I recently installed an application called Gitea <a href=\"/daily\/2024\/12\/01\/homelabbing-with-nixos\">on my homelab<\/a>.<\/p>\n\n<p>It's a service for hosting and managing Git repositories, similar to GitHub, GitLab and Bitbucket, but I'm hosting it on my own hardware and I'm in full control of my data.<\/p>\n\n<p>I've moved all of my client project code from private repositories in the Cloud to my Gitea instance, as well as some of my own private repositories for work-in-progress or archived projects.<\/p>\n\n<p>I plan to keep my open source project repositories on GitHub and Drupal.org, and use Gitea for personal and client project code, but I may move more to Gitea - like my website code and dotfiles - as time goes on.<\/p>\n\n<p>And, because I use NixOS for my homelab, installing Gitea was as easy as <code>services.gitea.enable = true<\/code>.<\/p>\n\n<p>There is also a Docker Compose image and Gitea Cloud, but running something like Gitea for your private code is something I'd like to see more Developers and agencies do.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>I recently installed an application called Gitea <a href=\"/daily\/2024\/12\/01\/homelabbing-with-nixos\">on my homelab<\/a>.<\/p>\n\n<p>It's a service for hosting and managing Git repositories, similar to GitHub, GitLab and Bitbucket, but I'm hosting it on my own hardware and I'm in full control of my data.<\/p>\n\n<p>I've moved all of my client project code from private repositories in the Cloud to my Gitea instance, as well as some of my own private repositories for work-in-progress or archived projects.<\/p>\n\n<p>I plan to keep my open source project repositories on GitHub and Drupal.org, and use Gitea for personal and client project code, but I may move more to Gitea - like my website code and dotfiles - as time goes on.<\/p>\n\n<p>And, because I use NixOS for my homelab, installing Gitea was as easy as <code>services.gitea.enable = true<\/code>.<\/p>\n\n<p>There is also a Docker Compose image and Gitea Cloud, but running something like Gitea for your private code is something I'd like to see more Developers and agencies do.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "1970-01-01T00:33:45+00:00",
|
|
"guid": null,
|
|
"hash": "ec1b7c6047417070fb9d7336a9849a98",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |