Homelab Maintenance Board for Nextcloud Deck
as a normal Nextcloud Deck board.
A maintenance board for a self-hosted server at home or in a small office. It sets a monthly rhythm for tested restores, security updates, and hardware that is close to failing.
Last verified
Board preview
Homelab Maintenance
Backlog1
Track hardware that is near end of life
Disks and batteries fail on a schedule you can predict. Replace them before they surprise you.
This Month2
Restore from backup, do not just check it ran
A backup job that reports success is not a backup until you have restored from it.
- Pick one service and restore it somewhere isolated
- Confirm the restored data is complete, not just present
- Time how long the restore took
- Write down the step you had forgotten
Apply security updates on a schedule
Unattended upgrades still need someone to read what changed and reboot when required.
- Review pending updates before applying them
- Apply to the least important host first
- Reboot if the kernel or runtime changed
- Check every service came back up
Doing1
Upgrade one service at a time
Two upgrades at once means you cannot tell which one broke the thing that broke.
Verify1
Check the service after every change
The change is not finished until you have used the service the way your household does.
- Log in as a normal user, not as admin
- Check the logs for new errors
- Confirm the backup job still runs after the change
Done1
Write down what you changed
Future you will not remember why that setting is unusual. Leave a note on the card.
View the portable v1 template JSON
{
"schema": "deckloud-template-v1",
"schemaVersion": 1,
"slug": "homelab-maintenance-nextcloud-deck",
"locale": "en",
"title": "Homelab Maintenance Board for Nextcloud Deck",
"description": "A maintenance rhythm for a self-hosted server: backups you have actually restored, security updates, and ageing hardware.",
"category": "software",
"tags": [
"self-hosted",
"homelab",
"maintenance"
],
"quickCreateStackKey": "backlog",
"compatibility": {
"requiresBoardCreate": true,
"includesAttachments": false,
"includesComments": false
},
"board": {
"title": "Homelab Maintenance",
"color": "0F766E"
},
"labels": [
{
"key": "backup",
"title": "Backup",
"color": "10B981"
},
{
"key": "security",
"title": "Security",
"color": "EF4444"
},
{
"key": "hardware",
"title": "Hardware",
"color": "64748B"
},
{
"key": "upgrade",
"title": "Upgrade",
"color": "3B82F6"
}
],
"stacks": [
{
"key": "backlog",
"title": "Backlog",
"order": 1
},
{
"key": "this-month",
"title": "This Month",
"order": 2
},
{
"key": "doing",
"title": "Doing",
"order": 3
},
{
"key": "verify",
"title": "Verify",
"order": 4
},
{
"key": "done",
"title": "Done",
"order": 5
}
],
"cards": [
{
"stack": "this-month",
"title": "Restore from backup, do not just check it ran",
"description": "A backup job that reports success is not a backup until you have restored from it.\n\n- [ ] Pick one service and restore it somewhere isolated\n- [ ] Confirm the restored data is complete, not just present\n- [ ] Time how long the restore took\n- [ ] Write down the step you had forgotten",
"labels": [
"backup"
],
"dueOffsetDays": 30
},
{
"stack": "this-month",
"title": "Apply security updates on a schedule",
"description": "Unattended upgrades still need someone to read what changed and reboot when required.\n\n- [ ] Review pending updates before applying them\n- [ ] Apply to the least important host first\n- [ ] Reboot if the kernel or runtime changed\n- [ ] Check every service came back up",
"labels": [
"security"
],
"dueOffsetDays": 7
},
{
"stack": "backlog",
"title": "Track hardware that is near end of life",
"description": "Disks and batteries fail on a schedule you can predict. Replace them before they surprise you.",
"labels": [
"hardware"
]
},
{
"stack": "doing",
"title": "Upgrade one service at a time",
"description": "Two upgrades at once means you cannot tell which one broke the thing that broke.",
"labels": [
"upgrade"
]
},
{
"stack": "verify",
"title": "Check the service after every change",
"description": "The change is not finished until you have used the service the way your household does.\n\n- [ ] Log in as a normal user, not as admin\n- [ ] Check the logs for new errors\n- [ ] Confirm the backup job still runs after the change",
"labels": [
"upgrade"
]
},
{
"stack": "done",
"title": "Write down what you changed",
"description": "Future you will not remember why that setting is unusual. Leave a note on the card.",
"labels": [
"hardware"
]
}
]
}
01
When to use this board
For anyone running their own server at home or in a small office, where maintenance is remembered only when something breaks. The board sets a rhythm around the three things that actually matter: a restore you have tested, security updates applied on a schedule, and hardware replaced before it fails.
02
How to run this board
Plan this month's restore and updates.
Keep the restore test and the security update cards in This Month and give them dates.
Change one service at a time.
Pull one upgrade into Doing, then move it to Verify and use the service the way your household does.
Note what you changed.
Write the reason for any unusual setting on the card before you move it to Done.
03
What this creates
5 stacks, 4 board labels, and 6 starter cards carrying 11 checklist steps. Attachments and comments are intentionally omitted so the template stays portable.
04
Why it fits Deckloud
The template is just a recipe for standard Deck objects. No hosted workflow account, no relay backend, and no Deckloud-only object model.
05
Safe import rules
IDs are not stored. Stack and label keys are remapped at creation time, due dates use relative offsets instead of stale fixed dates, and checklists are written into the card description as ordinary Markdown task lists.
FAQ
Practical questions
Does this change my Nextcloud server schema?
No. It creates ordinary boards, stacks, labels, and cards through the normal Deck model.
Does the template include comments or attachments?
No. V1 templates are text-only because comments imply authorship and attachments vary by server/version.
Can I edit the board after creating it?
Yes. After creation it is just a normal Nextcloud Deck board.
Why is restoring more important than backing up?
A backup job that reports success proves the job ran, not that the data is recoverable. The only proof is a restore you performed yourself.
Why upgrade one service at a time?
Two changes at once means you cannot tell which one broke things. Sequencing costs an evening; debugging a combined upgrade costs a weekend.
Related
Nextcloud Deck templates, made for real boards.
Free Nextcloud Deck board templates with starter cards and checklists: kanban, GTD, releases, bug triage, incidents, hiring, events, study, and more.
OpenBuild a Nextcloud Deck template without sending server data anywhere.
Build a simple Deckloud template JSON in your browser for a Nextcloud Deck board. No account, no upload, no server credentials.
OpenCreate templates that stay portable.
Create portable Nextcloud Deck board templates with stack keys, label keys, starter cards, and relative due dates.
Open