Biolink Script Hosting Requirements

Deploying a multi-tenant link-in-bio SaaS platform requires reliable hosting infrastructure. Knowing the exact biolink script hosting requirements ensures your application operates with high throughput, reliable SSL certificate routing, and fast response times on public creator profiles.

In this technical guide, we detail the complete hardware, operating system, PHP extension, and web server specifications needed to run Bibiolink on both standard cPanel shared hosting and dedicated Linux VPS servers.

Table of Contents

1. Core System Requirements Summary
2. Mandatory PHP 8.2 Extensions Checklist
3. cPanel vs. VPS vs. Docker: Choosing the Right Environment
4. Nginx Virtual Host Configuration for Subdomains and CNAMEs
5. Wildcard SSL Routing with Let's Encrypt / Certbot
6. MySQL Performance and Caching Optimizations
7. Pre-Flight Server Verification Script
8. Frequently Asked Questions

---

Bibiolink is engineered using standard, highly optimized web technologies. It does not require proprietary binary modules, exotic background workers, or bloated memory footprints.

| Component | Minimum Specification | Recommended Production Specification | | :--- | :--- | :--- | | Operating System | Linux (Ubuntu 20.04+, Debian 11+, AlmaLinux 8+) | Ubuntu 24.04 LTS | | CPU | 1 vCPU Core | 2 to 4 vCPU Cores | | RAM | 1 GB RAM | 2 GB to 4 GB RAM with Swap | | Disk Storage | 10 GB SSD / NVMe | 25 GB+ NVMe SSD | | PHP Version | PHP 8.2.0 or higher | PHP 8.2 or 8.3 with OPcache | | Database | MySQL 5.7+ or MariaDB 10.3+ | MySQL 8.0+ or MariaDB 10.6+ | | Web Server | Apache 2.4+ (with mod_rewrite) or Nginx | Nginx (Reverse Proxy with PHP-FPM) |

---

To ensure all builder modules, payment webhooks, image processing routines, and NFC vCard exporters execute without errors, verify that your PHP installation includes:

• pdo_mysql: Database communication driver.
• curl: Essential for Stripe, PayPal, and payment gateway API calls.
• openssl: Cryptographic token generation and webhook signature verification.
• mbstring: Multilingual character encoding and UTF-8 string handling.
• fileinfo: MIME type validation on uploaded logos and avatars.
• gd or imagick: Resizing and optimizing profile photos and generating dynamic QR codes.
• intl: Internationalized domain names (IDN) and date/currency formatting.
• zip: Software update archive extraction and batch export routines.

IonCube Requirement: None

Unlike many legacy marketplace scripts, Bibiolink requires zero IonCube or Zend Guard loaders. All source files are 100% human-readable text.

---

1. Shared cPanel / CloudLinux Hosting

• Best for: Low-budget initial launches (< 500 creator profiles).
• Setup: Select PHP 8.2 via MultiPHP Manager, enable required extensions via PHP Select Modules, and upload unencrypted script files to public_html.
• Limitation: Automated wildcard SSL certificate provisioning for custom CNAME domains may require manual DNS alias intervention depending on host policies.

2. Linux VPS (Ubuntu / Debian with Nginx)

• Best for: Commercial SaaS operators and agencies managing thousands of profiles.
• Setup: Full root control allows automated wildcard SSL certificates via Certbot, Redis caching, and instantaneous CNAME domain mapping.

3. Containerized Docker Deployment

• Best for: Enterprise infrastructure teams. Deploy using standard php:8.2-fpm and nginx:alpine containers linked to a managed MySQL instance.

---

To handle multi-tenant routing—where the application resolves the primary marketing site, dynamic user subdomains (user.yourdomain.com), and third-party custom domains (links.clientbrand.com)—use this production Nginx block:

server {
    listen 80;
    listen [::]:80;
    server_name yourdomain.com *.yourdomain.com;
    root /var/www/bibiolink/public;
    index index.php index.html;

    # Redirect standard HTTP to HTTPS
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name yourdomain.com *.yourdomain.com;
    root /var/www/bibiolink/public;
    index index.php index.html;

    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/var/run/php/php8.2-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        include fastcgi_params;
    }

    location ~ /\.ht {
        deny all;
    }
}

---

To provide SSL across all tenant subdomains, generate a wildcard Let's Encrypt certificate using DNS validation:

sudo certbot certonly --manual --preferred-challenges=dns \
  -d yourdomain.com -d "*.yourdomain.com"

For custom CNAME domains pointing from third-party client hosts (e.g., links.acme.com), Bibiolink is compatible with Cloudflare for SaaS (SSL for SaaS) or Certbot automated on-demand TLS termination. Review our multi-tenant custom domain biolink guide for architectural implementation steps.

---

To maintain sub-100ms response times during high-traffic creator campaign spikes:

1. Enable OPcache: Ensure opcache.enable=1 and opcache.memory_consumption=128 in your php.ini.
2. InnoDB Buffer Pool: Set innodb_buffer_pool_size in MySQL to approximately 60% of available server RAM on a dedicated VPS.
3. Database Indexing: Bibiolink includes pre-configured composite indexes on bio_pages.slug, custom_domains.domain_name, and page_blocks.bio_page_id to ensure instantaneous query execution.

---

You can verify your server's readiness directly from the command line:

php -r '
$reqs = ["pdo_mysql", "curl", "openssl", "mbstring", "fileinfo", "gd", "intl", "zip"];
$missing = array_filter($reqs, fn($ext) => !extension_loaded($ext));
echo version_compare(PHP_VERSION, "8.2.0", ">=") ? "PHP Version: OK (".PHP_VERSION.")\n" : "PHP Version: FAIL (Need 8.2+)\n";
echo empty($missing) ? "All extensions loaded successfully!\n" : "Missing extensions: " . implode(", ", $missing) . "\n";
'

---

Does Bibiolink work with PHP 8.3?

Yes. Bibiolink is strictly typed and fully compatible with both PHP 8.2 and PHP 8.3.

Can I run Bibiolink on LiteSpeed Web Server?

Yes. LiteSpeed and OpenLiteSpeed support standard PHP-FPM, .htaccess rewrite rules, and MySQL databases without issue.

Is root server access mandatory to run the script?

No. While root access on a VPS provides greater control over automated SSL certificates and server daemons, Bibiolink functions cleanly inside standard cPanel shared hosting accounts with standard database and file manager access.