chore: update project structure with contracts and services for CaddyManager, including configuration and Docker integration
All checks were successful
Caddy Manager CI build / docker (push) Successful in 1m16s
All checks were successful
Caddy Manager CI build / docker (push) Successful in 1m16s
This commit is contained in:
14
.cursor/rules/state-management.mdc
Normal file
14
.cursor/rules/state-management.mdc
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
alwaysApply: true
|
||||
---
|
||||
# State Management and Caching Strategies
|
||||
|
||||
## Caching Strategies
|
||||
- Implement in-memory caching for frequently used data, especially for Blazor Server apps. Use IMemoryCache for lightweight caching solutions
|
||||
- For Blazor, utilize EboloState (create the inheritance states where necessary) to cache application state between user sessions
|
||||
- Consider Distributed Cache strategies (like Redis or SQL Server Cache) for larger applications that need shared state across multiple users or clients
|
||||
- Cache API calls by storing responses to avoid redundant calls when data is unlikely to change, thus improving the user experience
|
||||
|
||||
## State Management Libraries
|
||||
- For server-side Blazor, use Scoped Services and the StateContainer pattern to manage state within user sessions while minimizing re-renders
|
||||
|
||||
Reference in New Issue
Block a user