GLWS · Hosting panels

AdminBolt.
On your own server.

Website, email, DNS and database management in a hosting dashboard.

What it is for.

Common uses of AdminBolt.

Common uses

  • Website administration
  • Hosting account organisation
  • Database and mail configuration

Keep in mind

Check supported operating systems and the separate commercial licence before installation.

Sizing and setup.

Planning examples, not official minimum requirements.

Hosting panels

Start with the whole stack.

Memory planning example
4 GB
Server environment
Linux / CPU-based VPS
Deployment method
Follow the publisher's documentation
Installed for you?
No. Your preference is saved with your configuration

Before you install

Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.

Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.

Read the AdminBolt documentation ↗ (opens in a new tab)

Things to decide before you install AdminBolt.

Advice specific to this application.

Separate the hosting control layer

A hosting panel coordinates several services rather than a single website. Inventory domains, mailboxes, databases and DNS zones before deciding how accounts should be arranged. Treat panel administrator access as access to the hosted stack, and retain a migration copy outside the machine.

Plan a reversible migration

Use a test account to check the target environment before moving customer data. Record the required runtime versions, scheduled tasks and DNS dependencies. A commercial panel licence and an actual hosting deployment are separate from choosing an application preference here.

Get the server ready.

Linux guides that help with this setup.

A repeatable deployment.

Four steps that make the environment easier to maintain.

  1. 01

    Check requirements

    Read the publisher's instructions and choose a supported installation method.

  2. 02

    Limit access

    Protect the dashboard, credentials and network endpoints before you expose any service.

  3. 03

    Persist your data

    Work out where the application keeps its state and store it separately from replaceable runtime files.

  4. 04

    Test recovery

    Back up the data and configuration, then check that you can restore them.

A checklist to keep.

Run through it before and after you install.

glws / application planningbash

$ application-checklist --name adminbolt

[ ] Supported deployment method

[ ] Authentication and access restrictions

[ ] Independent data backup

[ ] Updates and restoration tested

root@glws:~#

AdminBolt questions.

Quick answers before you choose resources.

Does choosing this application install it?

No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.

How much memory will I need?

Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.

Who maintains the application?

You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.

Where can I learn the server basics?

The knowledge base covers Linux access, packages, services, firewalls and backups.

Similar applications.

Other tools you might run alongside or instead.