Self-hosting means running an app on a computer you control and looking after that computer yourself. For a first attempt, choose something you can switch off for a day. Do not move the only copy of family photos, passwords or work documents onto a spare laptop just to try it.
Choose the smallest useful job
A home-only file tool or media library is easier to learn from than a service everyone needs all the time. Decide who will use it and whether they need access only at home. If you need it from anywhere on the internet, plan for a separate security task; do not forward a router port as a shortcut you do not understand. For a first project, keeping access inside the home network gives you less to manage.
What Docker solves, and what it leaves to you
Docker packages an app in a container. Docker Compose keeps its services, storage mounts and published ports in one readable file, so you can see the intended setup again. That file is a recipe, not a copy of your data. Docker says changes inside a container can disappear when the container is removed unless persistent storage is attached.
A named Docker volume can keep app data when the container is replaced, but it still lives on the same host. If that computer's drive fails, the volume is not an independent backup. Keep a separate copy and test that you can read it. Docker documents how volumes can be backed up and restored; the exact method depends on the app and whether it needs to be stopped first.
Write down four answers before starting
- What is the job? Pick one app and one non-critical set of test files. Know who will miss it if the computer is off.
- Where is the data? Record the volume or host folder, and where the separate backup goes. A Compose file alone cannot restore lost files.
- Who can reach it? Check the app's published port and your router settings. Keep administration behind a password and avoid internet exposure until you understand it.
- How will you maintain it? Plan operating-system and app updates, free-space checks, and a simple way to notice if the service stops.
Prove the backup before trusting the app
Create a disposable test file, make a backup to another drive or computer, and restore that file into a separate test location. Open the restored copy. This checks more than seeing a backup job say “complete,” and it leaves the live data untouched. If you cannot find or open the restored file, keep important data in its existing home for now.
After a week, ask whether the app restarted after a reboot, whether anyone could use it, and whether you could repeat the restore. If the routine is worth the control, continue. For a concrete next project, our old-laptop file-sync guide shows a local setup and a separate backup.
