Skip to main content

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 environmentCreate an environment
Add an app or a static siteAdd an app or static site
Ship a code changeDeploy a change
Use my own domain nameAdd a domain
Give an application more roomChange resources
See what went wrongRead logs
Find out why a deploy failed or an application misbehavesTroubleshoot a deploy or an application
Put an application back from a backupRestore a backup
Give a colleague accessInvite a user
Get mailboxes for my domainSet up email

Reference​

I want to…Read
Choose hosting capacity for my projectChoosing your hosting size
Compare current hosting pricesHosting prices
Get into the application and pick an environmentGetting started
Understand an environment and its shared poolYour environment
Work with an application's tabs, or sign in to WordPress/MoodleApplications
Deploy WordPress, Moodle, Laravel, Ruby or a managed serviceOther application types
Point names at applications, redirect a nameWeb addresses
Prove, register, renew or transfer a nameDomains
Add a mailbox to my mail clientEmail
Upload files over SFTP or use an SSH shellSFTP & SSH access
Read database addresses and credentialsDatabases
See what is backed upBackups and restores
Cancel hostingCancelling hosting
Get help from a personSupport

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.