Self-hosting for beginners
Understand self-hosting, choose a first project and learn the basics of server access, domains, updates and recovery before publishing.
What self-hosting means
Self-hosting means operating websites, applications or services on a server you control. That server can be a machine at home or a VM rented from a provider. The key difference is who manages the operating system, applications and data.
Dexlinkx is a control plane for that server. It helps with supported installation and management workflows while files remain on your host. The portal does not replace the machine, its network connection or the need for a recovery plan.
Pick a first project you can recover
Begin with something small and non-critical. A static test website lets you learn the path from server to browser before adding databases or exposing personal information.
Choose one host
Use a spare dedicated machine or VM. Check software and architecture compatibility first, and back up anything already stored there.
Keep independent access
Make sure you can access the local console or SSH. Store recovery information somewhere available if the portal or host is offline.
Run one test website
Verify a simple page locally. Add a public domain and HTTPS only after the basic site works.
Make a backup and restore it
Copy the files and any database to a separate destination. A restore test shows whether your backup can actually recover the project.
Create a maintenance routine
Review supported software updates, disk space, logs and backups. Use a test environment for changes that could break a public site.
The terms you will encounter
These parts have different jobs. Understanding the boundaries helps you troubleshoot without changing unrelated settings.
- Server: the physical machine or VM that runs your services.
- Domain and DNS: the name visitors use and the records that direct it to an address.
- HTTPS: the encrypted connection between a browser and the website, using a certificate for that hostname.
- Firewall: rules that control which network traffic is allowed.
- Database: application data stored separately from the website's program files.
- Backup: a recoverable copy of files and data stored outside the failure you are preparing for.
Home hardware or a hosted VM?
Home hardware gives you physical access and lets you reuse a suitable machine. You must plan for power, cooling, storage wear and the limitations of your internet connection. Check inbound connectivity before buying equipment for public hosting.
A hosted VM can avoid home-router constraints, but you still maintain the server software and need independent backups. Estimate the ongoing hosting, storage and bandwidth costs for your actual project rather than assuming either option is free.
Get started with Dexlinkx
Apply for the closed beta, prepare a supported machine and follow Dexlinkx Manager once approved. Start with one workload and confirm server status before using further actions.
The public introduction explains the preparation and connection flow. Detailed installation instructions remain available to signed-in beta users. Keep SSH or local access and use the server access profile to understand what the portal may manage.
Realistic expectations
- A dashboard simplifies supported tasks, but you still operate the host and network.
- Begin with a test workload before depending on self-hosting for important data or availability.
Apply for the closed beta
Apply for access and install your first server with Dexlinkx Manager once approved.