Documentation Index
Fetch the complete documentation index at: https://mintlify.com/QROkes/webinoly/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Webinoly provides automatic update capabilities for both the application itself and the underlying server stack (NGINX, PHP, MySQL/MariaDB).Update Webinoly
Check for Updates
Before updating, check if a new version is available:- Current Webinoly version
- Installed stack version
- Available stack version (if newer)
Standard Update
Update to the latest stable version:- Webinoly checks for the latest version via API
- Downloads the new version from official repository
- Runs migration scripts for version upgrades
- Updates configuration files
- Resets server configuration to latest optimized settings
- Verifies installation integrity
Update from Specific Version
Downgrade or upgrade to a specific version:Update from Branch
Install from development branch:Update Server Stack
Update the underlying LEMP stack components:- NGINX to latest version
- PHP to latest version
- MySQL/MariaDB to latest version
- System packages
- Dependencies
What Gets Updated
Webinoly Application
Updated components:- Core Webinoly scripts (
/opt/webinoly/) - Command-line tools (
webinoly,site,stack,httpauth,log) - Configuration templates
- Library functions
- Helper scripts
- Site files and databases
- SSL certificates
- User configurations
- Backup profiles
- Custom site configurations
Server Stack Components
NGINX:- Binary and modules
- Configuration files (regenerated with optimizations)
- Common configuration includes
- PHP-FPM and CLI
- PHP extensions
- Configuration files (regenerated with optimizations)
- Pool configurations
- Server binaries
- Configuration files (optimizations applied)
- No data changes
- Certbot (Let’s Encrypt client)
- Duplicity and Duply (backup tools)
- Redis server
- Memcached
- Postfix
- phpMyAdmin
Update Process Details
Pre-Update Steps
-
Backup Configuration: Webinoly automatically creates a backup:
- Version Validation: Checks current and target versions
- API Check: Verifies latest available version
During Update
- Download: Fetches update script from official repository
-
Migration: Runs version-specific migration scripts:
- Updates configuration format
- Migrates deprecated settings
- Updates system dependencies
- Regenerates configuration files
- Service Management: Automatically handles service restarts
- Verification: Runs integrity checks after update
Post-Update
After updating, Webinoly automatically:- Resets server configuration (see below)
- Verifies installation
- Shows update completion message
Migration Versions
Webinoly handles migrations automatically between versions:Major Version Migrations
v1.5.0 - phpMyAdmin Update- Removes old phpMyAdmin installation
- Installs newer phpMyAdmin version
- Updates Let’s Encrypt integration
- Adds zip utility
- Removes deprecated “ssl on” directive
- Updates swappiness configuration
- Backs up default NGINX file
- Creates apps.d directory
- Updates ACL configuration
- Adds HTTP authentication support
- Updates FastCGI parameters
- Removes debug pool configuration
- Updates admin tools structure
- Switches to official NGINX repository
- Updates package signing keys
- Migrates from PPA to official repo
- Removes Certbot from apt
- Installs Certbot via snap
- Updates SSL renewal configuration
- Migrates header configurations
- Updates site includes
- Renames admin tools folder
- Enables HTTP/3 for SSL sites
- Updates NGINX keys
- Updates boto3 for S3 backups on Ubuntu 24.04
- Updates MariaDB repository configuration
- Regenerates configuration file format
Update Verification
After updating, verify the installation:Update Failures
If Update Fails
If an update fails mid-process:- Check error message: Read the error output carefully
-
Review logs:
-
Restore configuration (if needed):
-
Re-run update:
-
Manual recovery:
Common Update Issues
API Unavailable- Check internet connectivity
- Retry after a few minutes
- Use specific version:
sudo webinoly -update=1.20.0
- Free up disk space before updating
- Remove old packages:
sudo apt clean
- Check snap is installed:
snap version - Manually install:
sudo snap install --classic certbot
- Regenerate config:
webinoly -server-reset=confile - Run verification:
webinoly -verify
Update Schedule
Recommended Update Frequency
Webinoly:- Check monthly for updates
- Apply security updates immediately
- Review changelog before major version updates
- Update quarterly or as needed
- Apply security patches promptly
- Test in staging environment first
- Apply security updates weekly
- Check for updates:
Rollback
Emergency Rollback
If an update causes critical issues:-
Restore configuration:
-
Downgrade packages (if needed):
-
Verify installation:
Best Practices
Before Updating
-
Backup Everything:
-
Note Current Versions:
- Check Changelog: Review changes in new version
- Schedule Maintenance Window: Plan for potential downtime
- Inform Users: Notify about maintenance
During Update
- Monitor Progress: Watch for errors
- Don’t Interrupt: Let update complete
- Save Output: Keep terminal output for reference
After Update
-
Run Verification:
- Test Sites: Check all sites are working
- Review Configurations: Check for reset settings
-
Check Logs: Look for errors
- Update Documentation: Note any manual changes needed
Automatic Updates
Webinoly does not automatically update itself. You must manually run updates.Why Manual Updates?
- Gives you control over update timing
- Allows review of changes before applying
- Prevents unexpected breaking changes
- Enables proper backup before updates
Optional Automation
If you want automated updates (not recommended for production):Update External Sources
Update external data sources (domain lists, timezones):- Public Suffix List (for domain validation)
- Timezone Database (for PHP timezone support)
Stay Informed
Keep track of updates:- GitHub Releases: https://github.com/QROkes/webinoly/releases
- Changelog: Review changes before updating
- Community: Join discussions about updates
- Newsletter: Subscribe for update notifications
Next Steps
- Troubleshooting - Fix update issues
- Server Management - Configure updated server
- Verify Installation - Check update success