Your automatically built server is installed, patched and secured. Now it needs a reason to exist. This page covers the three first jobs almost every small server gets — file sharing, a website, or apps — and how to prove each one actually works.
A new server tempts people in two wrong directions: leaving it idle “because it might be needed later”, or piling every job onto it on day one. The middle path is better: one main role, set up properly, proven working, and only then a second if the machine and the need are both real. Here are the three roles small offices and home labs actually start with.
The most common first job. The server holds one shared folder that every PC connects to, so files stop living in five copies on five desktops.
sudo apt install sambasudo mkdir -p /srv/shared, and set its owner to the people who will use it/etc/samba/smb.conf, restart the service with sudo systemctl restart smbdsudo smbpasswd -a username — share passwords are separate from login passwordsA web server turns the machine into the home of a site — a company page, an internal notice board, or a test copy of a real site.
sudo apt install nginx (Apache, with sudo apt install apache2, is the equally valid classic)/var/www/html and open the server’s address in a browser — the page should appearsudo ufw allow 'Nginx Full' on Ubuntu’s preset, or ports 80 and 443 directlyFor everything else — a media server, a dashboard, a small business app — containers are the modern default. Each app lives in its own sealed box, so apps stop breaking each other.
docker run hello-worldA file server, a website and three apps on one small machine will usually run — until the day the disk fills, an update reboots everything at once, or one app eats all the RAM and the file share dies with it. One main role per server keeps failures small and backups simple. Virtual machines and containers let one physical box host several separate servers, which keeps the rule without buying more hardware.
Once the video’s server is up, pick the one role your office or home actually needs and walk it through with this page.
▶️ Watch Full VideoTechnically yes, and many home servers do. The risk is shared fate: one failure, one full disk or one reboot takes every job down together, and backups get tangled. For anything a business depends on daily, keep the main role alone or separate the jobs into virtual machines or containers.
The one with a real user waiting. In most small offices that is the file share, because scattered files are the daily pain. A server built for a job nobody needs becomes shelfware within a month.
Inside your own network, a fixed address (set on the server or reserved in the router) makes shares and websites far more reliable, because other machines always find the server at the same place. For a purely home experiment, the automatic DHCP address works until it changes — then everything “breaks” at once.