Panel/docs/modules/UPDATE.md

Update Module

Role

Panel/modules/update exposes the admin Panel update page. The page delegates most update behavior to:

• Panel/modules/administration/panel_update.php

Current Behavior

The update page is intentionally simple:

• shows the installed Panel version
• shows the current git branch and commit when available
• exposes editable repository settings
• can create a backup
• can update from the configured repository and branch
• can roll back to an existing backup
• keeps Apache diagnostics in a collapsed Advanced Diagnostics section

Update Settings

The admin page stores these settings in the Panel settings table:

• gsp_update_repo_url
• gsp_update_branch
• gsp_update_repo_root
• gsp_update_panel_path
• gsp_update_backup_before

Defaults:

• Repository URL: http://forge.runlevelsystems.com/dev/GSP.git
• Branch: Panel-unstable
• Repository Root: /var/www/html/GSP
• Panel Path: /var/www/html/GSP/Panel
• Backup Before Update: enabled

Update Flow

1. Save or submit repository settings.
2. Validate repository URL, branch, repo root, and Panel path.
3. Run preflight against the configured paths.
4. Create a backup when enabled.
5. Clone the configured repository branch into a temporary checkout.
6. Sync files into the configured root/Panel paths.
7. Preserve Panel/includes/config.inc.php.
8. Run module updates/post-update hooks.
9. Write version metadata and LAST_UPDATE.txt.

Diagnostics

Apache and SSL checks are diagnostics only. Missing SSL certificates do not block Panel updates.

The old repeated SSL vhost disable buttons are not part of the primary update page. Apache path repair remains available under Advanced Diagnostics.

Remaining Issues

• The updater still contains legacy GitHub release helper code that is no longer rendered by the simplified primary UI.
• Real production testing should confirm file ownership and web-server permissions on /var/www/html/GSP.