Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Updating Server Resources are not applied on the fly #1025

Open
notAreYouScared opened this issue Feb 22, 2025 · 0 comments
Open

Updating Server Resources are not applied on the fly #1025

notAreYouScared opened this issue Feb 22, 2025 · 0 comments
Labels
🐛 bug Something isn't working

Comments

@notAreYouScared
Copy link
Member

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.
@notAreYouScared notAreYouScared added the 🐛 bug Something isn't working label Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐛 bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@notAreYouScared