Updating Server Resources are not applied on the fly #262

Closed
opened 2026-02-05 17:21:36 +03:00 by OVERLORD · 0 comments
Owner

Originally created by @notAreYouScared on GitHub (Feb 22, 2025).

When updating a server CPU/ram/disk limits, It should be updated on the fly without having to restart the container, there is existing functionality that was not added back in with the filament change.

Appears BuildModificationService needs to be called once the server record is updated.

Originally created by @notAreYouScared on GitHub (Feb 22, 2025). When updating a server CPU/ram/disk limits, It should be updated on the fly without having to restart the container, there is existing functionality that was not added back in with the filament change. Appears `BuildModificationService` needs to be called once the server record is updated.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#262