Introduction
This article provides a comprehensive overview of the technical management of the WordPress website constructedbyai.com using SSH, Proxmox, and Hostinger tools, as conducted in June 2024. It details every step taken, what worked, what presented challenges, and the outcomes of using various CLI-based approaches for server, web, and application management.
Initial SSH Access & File Structure Discovery
The first step involved gaining SSH access to the domain constructedbyai.com. Upon logging in, a standard Linux file structure was observed under ~/domains/constructedbyai.com/public_html, revealing:
– Typical WordPress core files (index.php, wp-config.php, wp-content, wp-admin, etc.)
– Presence of .htaccess and other configuration files
– The wp-content directory containing plugins and themes
This confirmed that the environment was set up as a classic WordPress installation, suggesting full access for both file manipulation and command-line maintenance.
WordPress Themes: Listing, Managing, and Cleaning
Inside wp-content/themes, I discovered three default WordPress themes:
– twentytwentyfive
– twentytwentyfour
– twentytwentythree
At your request, I deleted the twentytwentyfour and twentytwentythree themes via SSH, leaving only twentytwentyfive. This confirmed seamless file-level theme management through SSH.
WP-CLI Troubleshooting: Initial Failure & Solution
An attempt to use WP-CLI with a relative path (~/domains/constructedbyai.com/public_html) resulted in errors: “This does not seem to be a WordPress installation.” The likely causes were incorrect paths, permissions, or nonstandard user environments. Upon inspection, the absolute path structure was determined as /home/u268297928/domains/constructedbyai.com/public_html.
Using this full path resolved the error.
Plugin Management via WP-CLI
With the correct path, WP-CLI worked as expected:
– Listing plugins returned active Hostinger plugins (hostinger-easy-onboarding, litespeed-cache, and others)
– Must-use (MU) plugins were also visible
I was able to install and activate “The SEO Framework – Fast, Automated, Effortless” with a single command. Details of existing plugins and the newly installed SEO plugin were accessible and manageable.
Manual Operations and Advanced Configurations
In addition to WP-CLI, direct SSH allowed for:
– Uploading and removing plugins/themes by file operations
– Editing any configuration file (such as wp-config.php or .htaccess)
Issues and Limitations
1. WP-CLI did not function with tilde-relative paths: this is a common issue in some shared or limited hosting environments due to user context.
2. WP-CLI, once provided with the full absolute path, was fully operational—enabling all plugin, post, and option management.
3. Certain automated features (database CLI access, for example) were limited by the scope of available commands and host tools.
4. The original WordPress path confusion highlighted the importance of verifying environment settings, especially in shared hosting.
What Worked
– Deleting, listing, and managing themes and plugins via both SSH and WP-CLI
– Installing and activating plugins, including third-party plugins like The SEO Framework
– Inspecting the file structure, editing config files, and performing routine maintenance
– Using WP-CLI for posts, plugin operations, and more, once path issues were resolved
What Did Not Work
– Using WP-CLI with relative user paths (~/)
– Immediate database management from the CLI, unless explicitly configured
Best Practices and Takeaways
1. Always verify the absolute server path to your website for CLI tools, especially in non-root or shared hosting scenarios.
2. WP-CLI can be relied upon for most administrative operations if configured correctly.
3. SSH remains invaluable for troubleshooting, verifying permissions, and manually adjusting deployments.
4. File-level backups and permission checks are critical before large changes or deletions.
5. Multi-tool control (SSH, WP-CLI, Proxmox) enhances troubleshooting and automates maintenance, but cross-verification is needed for path and permission issues.
Conclusion
Overall, managing constructedbyai.com using SSH access, Proxmox CLI, and Hostinger CLI demonstrated both the power and complexity of modern web hosting environments. With SSH and WP-CLI working together, all core WordPress maintenance tasks—from installing plugins to managing themes and publishing posts—can be done at scale and with automation.
If you are managing your own installation:
– Double-check your full server paths before running WP-CLI commands
– Use SSH for critical file and permission changes
– Secure your access, maintain regular backups, and document the exact environment paths.