Where every setting lives: configuring your ByteNests resources
A tour of the settings for VMs, hosting, domains, object storage, databases, apps, the registry and game servers, and what each one changes.
Creating a resource takes a minute. Most of the real work is the configuration afterwards: who can reach it, how it is backed up, and what happens when something changes. This is a map of where those settings are, one product at a time.
Virtual machines
Firewall: VM → Firewall: Incoming and outgoing rules, checked top to bottom. Quick setup applies a ready-made set such as SSH, HTTP and HTTPS.
Disks: VM → Disks: Attach a disk from 1 to 2048 GB, detach one, or choose the boot disk.
Backups and snapshots: VM → Backups: Take a backup or snapshot now, restore or roll back.
Power: Top of the VM page: Start, Stop (keeps disks) and Reboot.
SSH keys and images: Settings → SSH keys, Settings → Custom images: Keys offered when you create a VM; upload a disk image or save a stopped VM as a template.
CPU and memory are fixed once a VM exists. To move to a bigger size, create a new VM and move your data. See Manage a VM.
Web hosting
PHP version and handler: Websites → Manage: Restarts PHP for that site only. Check your app supports the version first.
SSL and Force HTTPS: SSL tab: Issue a free Let’s Encrypt certificate and send http:// visitors to https://.
Subdomains: Domains tab: A subdomain gets its own folder, PHP version and certificate.
Mailboxes and forwarders: Email tab: Quotas, forwarding a copy, disabling a mailbox, and the SPF, DKIM and DMARC check.
Databases: Databases tab: MySQL databases, extra users and phpMyAdmin.
FTP: FTP tab: Accounts for all your files or a single folder, with an optional quota.
Traffic: Traffic → Settings: Counting per site, exclusions, who can see the numbers, alerts and how long data is kept.
Domains
DNS records: A, AAAA, CNAME, MX, TXT and NS records. Saving publishes the whole record set. See DNS records and nameservers.
Nameservers: keep ByteNests DNS, or point the domain at another DNS provider. With custom nameservers, records here stop applying.
Auto-renew: on or off per domain, from the domain list or its settings.
Object storage
Access: private (signed requests and share links only) or public read.
Versioning: keep older copies when files are overwritten or deleted.
Limits: size and object limits with emails at 80% and 95%.
Lifecycle rules: delete files under a prefix after a number of days.
CORS: let web pages on other domains load or upload files.
Access keys: per-bucket permissions, an expiry and allowed IP addresses for each key.
Object lock is the one setting that must be chosen when the bucket is created.
Managed databases
Trusted sources: the IP addresses, ranges or VMs allowed on the public endpoint.
Users & databases: a user per app, password resets, extra databases.
Resize: change the size, with a few minutes of downtime while the server restarts.
Add storage: more disk with no downtime. It cannot shrink later.
Maintenance window: the weekly hour, in UTC, when patches roll out.
App Platform
Components: add a web service, worker, static site or pre-deploy job. Each change starts a new deployment.
Environment variables: shared by all components. Secrets are encrypted and cannot be read back.
Size and instances: two or more instances keep the app up during deploys.
Domains: add your own domain with a CNAME record, and pick the primary one.
Deploy on push: a webhook for GitHub or GitLab, or automatic redeploys when you push a new image to your registry.
Container registry
Storage limit: a cap, not a charge. You pay only for what you store.
Scan on push: check every new image for known vulnerabilities.
Cleanup rules: remove old or untagged images daily, keeping the ones you choose.
Access tokens: one per person or pipeline, revocable at once.
Game servers
Game servers are configured from the Console on the server page, with Start, Stop and Restart at the top. See Run your own Minecraft server for the commands most people need.
Account-wide settings
Settings → Security: two-factor authentication.
Settings → Team: invite people as Admin, Member or Viewer.
Settings → API tokens: full-access or read-only tokens for the CLI and API.
Billing → Settings: a monthly budget alert and your billing details.