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.
Common tasks
Each task has one short page, in the panel's own words:
| I want to… | Read |
|---|---|
| Create an environment | Create an environment |
| Add an app or a static site | Add an app or static site |
| Ship a code change | Deploy a change |
| Use my own domain name | Add a domain |
| Give an application more room | Change resources |
| See what went wrong | Read logs |
| Find out why a deploy failed or an application misbehaves | Troubleshoot a deploy or an application |
| Put an application back from a backup | Restore a backup |
| Give a colleague access | Invite a user |
| Get mailboxes for my domain | Set up email |
Reference
| I want to… | Read |
|---|---|
| Choose hosting capacity for my project | Choosing your hosting size |
| Compare current hosting prices | Hosting prices |
| Get into the application and pick an environment | Getting started |
| Understand an environment and its shared pool | Your environment |
| Work with an application's tabs, or sign in to WordPress/Moodle | Applications |
| Deploy WordPress, Moodle, Laravel, Ruby or a managed service | Other application types |
| Point names at applications, redirect a name | Web addresses |
| Prove, register, renew or transfer a name | Domains |
| Add a mailbox to my mail client | |
| Upload files over SFTP or use an SSH shell | SFTP & SSH access |
| Read database addresses and credentials | Databases |
| See what is backed up | Backups and restores |
| 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.