Skip to content

Refactor Config Loading, Optimize Dashboard, and Fix Nextcloud Config#205

Open
Cylae wants to merge 1 commit intomainfrom
refactor-and-optimize-v1.0.8-4109007814059015812
Open

Refactor Config Loading, Optimize Dashboard, and Fix Nextcloud Config#205
Cylae wants to merge 1 commit intomainfrom
refactor-and-optimize-v1.0.8-4109007814059015812

Conversation

@Cylae
Copy link
Owner

@Cylae Cylae commented Feb 25, 2026

This PR includes several improvements and fixes:

  1. Configuration Loading: Updated Config::load and Config::load_async to check for config.yaml in /opt/server_manager/ if it doesn't exist in the current directory. This aligns with UserManager behavior. The caching logic now correctly tracks the loaded file path.
  2. Dashboard Optimization: The system statistics refresh (CPU, Memory, Disks) in the web dashboard is now wrapped in tokio::task::spawn_blocking. This prevents the heavy synchronous sysinfo calls from blocking the async executor, improving responsiveness.
  3. Nextcloud Security: Added escaping for $ characters in the Nextcloud PHP autoconfig generation. This prevents passwords containing $ from being misinterpreted as PHP variables.
  4. Version Update: Bumped the project version to 1.0.8 in Cargo.toml and updated the README.md badge.

PR created automatically by Jules for task 4109007814059015812 started by @Cylae

… security

- Refactor `Config::load` and `Config::load_async` to support `/opt/server_manager/config.yaml` as a fallback path and correctly manage caching with file path awareness.
- Optimize web dashboard by wrapping blocking `sysinfo` refresh in `tokio::task::spawn_blocking` to prevent blocking the async runtime.
- Fix potential security issue in Nextcloud configuration by escaping `$` characters in generated PHP autoconfig to prevent variable interpolation.
- Bump version to 1.0.8 in `Cargo.toml` and `README.md`.
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant