Hosting documentation
HaakCo Hosting runs your websites and applications for you. You get an account, one or more environments, and a set of applications inside each environment — with their own addresses, their own administrator logins, their own database, and backups.
These pages describe what you do in the Hosting application at hosting.haak.co. They are written for the person who runs the site, not for the person who runs the cluster.
Where to start
| I want to… | Read |
|---|---|
| Get into the application and pick an environment | Getting started |
| See whether an environment is healthy, or retry a change | Your environment |
| Open a site or sign in to WordPress/Moodle as an administrator | Applications |
| Use my own domain name | Domains |
| Upload files over SFTP or use an SSH shell | SFTP & SSH access |
| Read database addresses and credentials | Databases |
| See what is backed up, and ask for a restore | Backups and restores |
| Read an application's log output | Logs |
| Cancel hosting | Cancelling hosting |
| Get help from a person | Support |
What is yours, and what we look after
You decide:
- your applications' addresses, including a domain name you already own;
- application administrator passwords, and who may sign in where;
- SFTP/SSH logins for your environment;
- how your environment's CPU, memory and storage are divided between your workloads;
- whether you want to stop hosting, and on what date.
We look after:
- the cluster your environment runs on;
- the pinned application images and their upgrades;
- the database engine and how its instances stay in agreement;
- the backup schedule and where backups are stored;
- TLS certificates for your addresses.
You never edit infrastructure directly. Everything you change in Hosting is stored, and then applied for you.