Skip to content

Cyberfusion Docs

Start with All about projects. A project is one website or application, and it's the page you'll spend most of your time on. Everything else here is either a task you'll do to a project, or one of the parts a project is built from.

Or search, if you already know what you're after.

Something broken right now?

Core

Start here

  • Projects

    One project is one website or application. What the templates set up for you, what's on the project page, and how to import one that already exists.

  • Staging environments and cloning

    A second copy to break safely, and what 'Clone' does and doesn't copy over to production.

  • Let's Encrypt certificates

    Free, automatic HTTPS. How it's issued and renewed, and what to check when a certificate doesn't appear.

  • Run a Node.js application

    Web-accessible via Passenger, or background-only as a daemon.

  • Set up a WordPress multisite

    Subdirectory, subdomain (wildcard alias), or domain mapping, plus the SSL caveat for wildcards.

Run it day to day

  • Crons

    Scheduled commands. WP-Cron and Laravel Scheduler presets, and what the failure emails mean.

  • Backups

    Three backup tracks and what you control on each. Creating, browsing and restoring an archive yourself.

  • Databases

    MariaDB and PostgreSQL. Backups, encryption at rest, weekly optimisation.

  • Change or disable a UNIX user's password

    Rotate the SSH and SFTP password, or turn it off so only keys work.

  • Set up basic authentication

    Put a username and password prompt in front of a site, or one path inside it.

Keep an eye on things

  • Health checks

    Automated checks per cluster: outdated versions, missing security settings, performance settings. Every open issue has a button that takes you to the fix.

  • CMS versions

    Every CMS found on your clusters, its version, and whether that version still gets security updates.

  • Scheduled actions

    Node upgrades you set to run at a quiet moment. Where to find them, and how to reschedule or cancel.

When something goes wrong

Make it faster

  • Prepare for peak traffic

    Before Black Friday or a sale: read your baseline, size 'Max Children', check the limits, move bulk mail off the cluster.

  • InnoDB buffer pool

    When the database no longer fits in memory, queries read from disk and everything slows down. How to see both numbers and what to do.

  • FPM pools

    What runs a site's PHP code. Sizing for peak, memory and CPU caps, slow-request logging, restart vs reload.

  • Redis

    In-memory store for caches, sessions and queues. The eviction policy to pick, and the one that loses jobs.

  • PHP performance monitoring with Tideways

    Find out which requests and queries are slow. Enabling it, the free workshop, and paid help.

WordPress and WooCommerce

  • WordPress database indexes

    WordPress ships without several indexes it needs to stay fast. Add the missing ones in one click.

  • Server wp-cron

    Move WordPress's scheduled tasks off your visitors' page loads, so they also run when nobody visits.

  • WooCommerce HPOS

    Whether your shop stores orders in their own tables, and what changes when it does.

Configure

  • Change PHP settings

    Cluster-wide, per site, or per directory via .user.ini.

  • Passenger apps

    Node.js, Ruby or Python applications. App root, environment variables, sizing.

  • Custom config snippets

    Reusable nginx or Apache config, with the ordering rule that decides which setting wins.

  • Install Puppeteer

    Enable Puppeteer support on the cluster and install it in your project.

  • Hosts entries

    Internal hostnames like redis.internal that resolve on every node in the cluster.

Security and compliance

  • Security and auditing

    What's encrypted at rest, what a node records on SSH login, the logs Core keeps of every change, and restricting API access by IP.

  • Separating services across nodes

    What a break-in reaches when the web server, database and mail share a node, what separating them prevents, and what it costs.

  • Standards scans

    Automatic compliance scans of your domains against the open internet standards, and when tenders ask for them.

  • security.txt policies

    Tell security researchers how to report a vulnerability. One policy, many domains.

  • Basic authentication

    The concepts behind the password prompt: htpasswd file, htpasswd users, realm, and the Apache vs nginx scoping difference.

  • carbon.txt

    Publish your sustainability disclosures and upstream services where auditors and customers can find them.

Under the hood

The objects a project is built from. Reach for these when you need to change one specific part, or when a setup doesn't fit the project model.

  • UNIX users

    The account that owns one site's files and processes. Daemons, usage tracking, malware scanning.

  • UNIX user namespacing

    Why your chosen PHP version is always the one that runs, why sudo doesn't work, and the one reason to opt out.

  • Virtual hosts

    Serve a domain from a directory on disk. Language choice, and the automatic reload that picks up a new release.

  • Domain routers

    Per-domain routing: which node serves traffic, which certificate is presented, who's allowed in.

  • URL redirects

    Send one domain to another. Path and query handling, server aliases, status codes.

  • FTP users

    An extra login limited to one directory. Why to avoid FTP, and the two cases where you still need it.

  • Firewall rules

    Per-server allow-list rules. Source by IP or group, target by service or port.

  • HAProxy listens

    Expose MariaDB, PostgreSQL, Meilisearch, SingleStore or RabbitMQ on a port or socket.

  • Run a custom internet-facing service

    A websocket server, MQTT broker or custom API, supervised as a daemon and opened up to the internet.

  • Add a node group

    Add a node group, such as Puppeteer or Node.js, to a node.

Mail

Platform