Docs › Daily use
Daily use for IT administrators
Five minutes a day and a short weekly check keep MCDock healthy, backed up, secure and licensed.
For the first set-up, see the quick start for IT administrators.
Every day (5 minutes)
- IT admin → Control center: every item should be green. Check the last backup, the NAS copy, free disk space, repository health, the runners and the licence.
- Read the admin alerts in e-mail or Teams: failed backups, low disk, health problems and upgrade results.
- Look at Users for locked accounts, and help people who lost their 2FA phone. They can use a recovery code.
Every week
- Check the result of the weekly restore test. A backup you have never restored is only a hope.
- Look at Repository health. Run Fix it (guided) for any repository with problems. It makes a safety copy first.
- Look at Storage. Act at 85% full. Pushes pause below 2 GB free, while clone and pull keep working.
- Read the audit log for admin changes, new tokens and failed sign-ins. Forward it to your SIEM if you have one.
Every month
- Upgrades: install new releases. They are signed, they make a backup first, and rollback is one click. Upgrades never change your data, licence or database settings.
- Access review: remove leavers and check the team memberships with each head of department.
- Check that the certificate, the service account and the NAS share are all still valid.
Licence
- IT admin → Licence shows the status, the end date and the last check-in with mcdock.dev. Online licences renew by themselves every year.
- Each mcdock.dev account can hold the licence for one MCDock server. See Licensing and activation.
When something goes wrong
- The database doesn't answer: open the recovery page shown on the server. Git keeps reading meanwhile.
- Disk full: free some space, or run the Git LFS clean-up. Unused files go to a 30-day quarantine first.
- You need help: ask in the community. Report security issues privately to security@mcdock.dev.
Updated 21 Nov 2026 · Something missing? Ask in the community.