{ "uuid": [ { "value": "dabbd6ba-8fd9-45dd-98f5-27aa3804dd46" } ], "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:34+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": "Why keep a dotfiles repository\n" } ], "created": [ { "value": "2023-08-14T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T09:00:34+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2023\/08\/14\/why-keep-a-dotfiles-repository", "langcode": "en" } ], "body": [ { "value": "\n

A few days ago, I said it's been 8 years since I started my dotfiles repository and kept my configuration files in version control.<\/p>\n\n

But why do this?<\/p>\n\n

It makes it easy to share the same configuration across multiple computers, such as personal and work or different setups for clients.<\/p>\n\n

It's also a backup of my configuration. If I need to reinstall my system or start fresh, I don't need to configure everything again manually.<\/p>\n\n

If you work on a team, you can share your configuration with colleagues, find things that work well for the team, and anything that could cause issues.<\/p>\n\n

I can experiment with settings and programs and then revert them again if I want to.<\/p>\n\n

If I add or remove a program or change a setting, I have the Git commit log to refer to, and I can document why I made that change and what problem it solves in the message body.<\/p>\n\n

I can review it in the future in case I need it again or want to re-evaluate it.<\/p>\n\n

Like on other projects, capturing the why is important. The what can be seen in the diff and speaks for itself, but it doesn't explain why I made the change and won't help if I look at that commit in the future.<\/p>\n\n ", "format": "full_html", "processed": "\n

A few days ago, I said it's been 8 years since I started my dotfiles repository and kept my configuration files in version control.<\/p>\n\n

But why do this?<\/p>\n\n

It makes it easy to share the same configuration across multiple computers, such as personal and work or different setups for clients.<\/p>\n\n

It's also a backup of my configuration. If I need to reinstall my system or start fresh, I don't need to configure everything again manually.<\/p>\n\n

If you work on a team, you can share your configuration with colleagues, find things that work well for the team, and anything that could cause issues.<\/p>\n\n

I can experiment with settings and programs and then revert them again if I want to.<\/p>\n\n

If I add or remove a program or change a setting, I have the Git commit log to refer to, and I can document why I made that change and what problem it solves in the message body.<\/p>\n\n

I can review it in the future in case I need it again or want to re-evaluate it.<\/p>\n\n

Like on other projects, capturing the why is important. The what can be seen in the diff and speaks for itself, but it doesn't explain why I made the change and won't help if I look at that commit in the future.<\/p>\n\n ", "summary": null } ], "feeds_item": [ { "imported": "1970-01-01T00:33:45+00:00", "guid": null, "hash": "d5ed61ce59348374630aa49fea8f3709", "target_type": "feeds_feed", "target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76" } ] }