Documentation
MCDock documentation
Install, run and secure MCDock on your own servers.
Getting started
- Install MCDockFrom an empty Windows server to a running MCDock in about ten minutes.
- Quick start for IT administratorsAbout 30 minutes from a fresh install to a secured, backed-up and activated server.
- Quick start for engineersConnect your PC, clone, lock large files and open pull requests.
Daily use
- Daily use: who does whatWhat engineers, heads of department, DevOps engineers and IT administrators do in MCDock each day.
- Daily use for developersYour day in MCDock: My work, branches, pull requests, reviews, large files and pipelines.
- Daily use for heads of departmentApprove work, follow progress, manage your team and keep an audit trail, without touching Git.
- Daily use for DevOps engineersPipelines, runners, environments, variables, merge gates and releases.
- Daily use for IT administratorsFive minutes a day and a short weekly check keep MCDock healthy, backed up, secure and licensed.
Running MCDock
- Backups and restoreTwo kinds of backup, a NAS copy, restore tests and restoring only what you need.
- Upgrades and rollbackSigned releases only, a safety backup first, and one-click rollback.
- Database and standby serverSQLite by default, PostgreSQL with a standby for production.
- Repository health and repairNightly checks, guided repair and recovering missing data.
- NotificationsBell, e-mail and Microsoft Teams.
- Storage and Git LFS clean-upFree space, alerts and a safe clean-up of unused large files.
Licensing
- Licensing and activationFree, one year at a time, renewed automatically.
Security
- Security hardening checklistThe settings to check before you go live.
Reference
- Command lineService, backup and recovery commands.
- Release historyWhat changed in each MCDock version.