# Update

Workspace reference: [`GSP-WORKSPACE.md`](../../../GSP-WORKSPACE.md)

## Purpose

Panel update and patch management.

## Current Status

- Production
- Admin-only

## Dependencies

- patch and update logs
- admin access

## Database Tables

- `update_blacklist`
- `panel_update_log`
- `update_patches`

## Agent Interaction

- indirect if patch operations touch remote systems

## User Workflow

- none, admin-only

## Admin Workflow

- inspect and apply updates
- review patch logs

## Security Concerns

- updates modify the control plane itself

## Known Issues

- can be confusing if not clearly separated from game-server updates

## Missing Functionality

- richer update history and rollback guidance
- clearer operator documentation around backup counts and derived settings

## Suggested Future Improvements

- keep admin-only and document carefully
- add richer update history summaries if the page later needs deeper audit visibility

## Recommendation

- Keep

## Current GSP Additions

The primary update implementation lives in `Panel/modules/administration/panel_update.php` and is exposed by `Panel/modules/update/update.php`.

Current update targets:

- Panel files only in the active admin UI

Active UI behavior:

- Repository Root is the primary deployment path setting
- Panel Path is derived internally as `Repository Root + /Panel`
- Panel Source Folder is fixed to `Panel`
- Git Executable is hidden and defaults to `git`
- Post-update Command remains available only as an advanced field