How to Use InitOps – Deploy a Production-Ready WordPress Server with a Single Command

InitOps was built to simplify that entire workflow. Instead of manually configuring every component, InitOps automatically deploys and optimizes a complete WordPress production stack on Ubuntu 24.04 LTS within minutes.

Step 1: Connect to Your VPS as Root

First, connect to your Ubuntu VPS using SSH:

ssh root@your-server-ip

InitOps requires root privileges because it automatically installs packages, configures services, modifies system files, and applies security rules. If the script is not executed as root, it will immediately stop.

Step 2: Install InitOps

After connecting to the server, run:

curl -sSL https://inithtml.com/initops/install.sh | bash

The installer will automatically:

• Update the operating system.
• Install Python3 and Curl.
• Download the InitOps deployment engine.
• Validate the Python source code.
• Apply executable permissions.
• Launch the InitOps management menu.

Everything runs automatically without requiring manual configuration.

Step 3: Start the Deployment Process

Once InitOps launches, you will see the main menu:

[1] Deploy LEMP Stack & WordPress
[2] Re-apply Performance Optimizations
[3] Help & Tuning Paths
[0] Exit

To deploy a new WordPress server, choose:

1

Step 4: Enter Your Website Information

InitOps will ask for several basic parameters:

1. Domain name.
2. Database name.
3. WordPress table prefix.

Example:

-> Domain name: site.com
-> Database name: wp_production
-> Table prefix: wp_

The database username and password are automatically generated using secure cryptographic methods to reduce the risk of brute-force attacks or predictable credentials.

Step 5: Wait for Automatic Deployment

InitOps will now automatically install and configure:

• Nginx.
• MariaDB.
• PHP 8.3 FPM.
• Redis Server.
• Fail2Ban.
• Iptables Firewall.
• WordPress Core.
• WP-CLI.
• Certbot SSL.

At the same time, the system automatically applies:

• Nginx performance tuning.
• PHP-FPM optimization.
• MariaDB tuning.
• Redis Unix Socket configuration.
• Production-grade security rules.
• System Cron replacement for WP-Cron.

All optimizations are based on the actual RAM and CPU resources available on the VPS.

Step 6: Complete the WordPress Setup

After deployment finishes successfully, InitOps will display:

• Database Name.
• Database User.
• Database Password.
• Table Prefix.
• Web Root Path.

Save these credentials carefully because the system will not display them again for security reasons.

Step 7: Install SSL with Certbot (VERY IMPORTANT)

This is one of the most important steps after deployment.

Even though InitOps already installs Certbot automatically, HTTPS is not enabled until you manually run the SSL command.

Once your domain points to the VPS IP address, run:

certbot --nginx -d domain.com

If your website also uses the www subdomain:

certbot --nginx -d domain.com -d www.domain.com

InitOps already installs:

• Certbot.
• Python3 Certbot Nginx integration.

so SSL configuration will be automatically injected into Nginx.

Afterward, open your domain in a browser to finish the WordPress installation wizard.

Important Note for Cloudflare Users

If you use Cloudflare, make sure you:

• Point the domain to your VPS IP address first.
• Keep the Cloudflare icon in gray cloud mode (DNS Only).

This is extremely important for successful Let’s Encrypt HTTP validation.

If the orange proxy cloud is enabled too early, Certbot may fail because requests are routed through Cloudflare instead of reaching the VPS directly.

After SSL installation completes successfully, you can safely enable the orange cloud again if you want CDN caching or DDoS protection.

How to Reopen InitOps Later

After the first installation, you no longer need to run the long curl command again.

Simply type:

initops

from any directory to reopen the management menu.

What to Do After Upgrading VPS Resources

If you later upgrade your VPS RAM or CPU resources, reopen InitOps and select:

[2] Re-apply Performance Optimizations

InitOps will automatically detect the new hardware specifications and re-optimize:

• Nginx.
• PHP-FPM.
• MariaDB.
• Redis.

to fully utilize the upgraded server resources.

How to Apply Advanced Tuning

If you want to access all tuning file locations, choose:

[3] Help & Tuning Paths

This section displays:

• Nginx configuration paths.
• PHP-FPM pool configuration.
• MariaDB tuning files.
• Redis configuration.
• WordPress configuration.
• System Cron setup.

This menu is intended for advanced tuning and deeper server customization after deployment.

Note: To ensure all WordPress files and directories keep the correct ownership after completing all configuration or manual changes, it is recommended to run the following command again:

chown -R www-data:www-data /var/www/html

This helps prevent unexpected permission-related issues during production usage.

Conclusion

InitOps transforms what would normally be hours of manual Linux and WordPress server configuration into a streamlined automated deployment process. With a clean Ubuntu 24.04 VPS, a single installation command, and a final Certbot SSL step, you can quickly deploy a fast, secure, and production-ready WordPress environment.