Skip to content

Conversation

@stolkie
Copy link
Contributor

@stolkie stolkie commented Sep 6, 2025

This release has a set of quality of life updates that will hopefully greatly improve everyone's experience with CaddyManager, thank you all for playing around with it thus far!

New features

Improvements

stolkie added 30 commits June 30, 2025 02:27
…istent

feat: Update API routes to include versioning and adjust Swagger docu…
…rences-from-readme

Chore/remove basic auth references from readme
- Added `caddyServersRepository.js` to abstract data access for Caddy servers, supporting both Mongoose and SQLite.
- Added `userRepository.js` for user data access, also supporting Mongoose and SQLite.
- Refactored `auditService.js` to utilize `auditLogRepository` for logging and retrieving audit logs.
- Updated `caddyService.js` to use the new Caddy servers repository for CRUD operations.
- Introduced `sqliteService.js` for SQLite database connection and user management.
- Created `test-all-engines.sh` script for running integration tests across SQLite and MongoDB.
- Updated various service files to replace direct model interactions with repository methods.
- Added mongodb-memory-server as a dev dependency to facilitate in-memory MongoDB for testing.
- Updated mongoService to connect to either production MongoDB or in-memory MongoDB based on the environment.
- Implemented disconnect logic for the in-memory MongoDB server.
- Enhanced apiKeyRepository with additional methods for CRUD operations and user association.
- Created comprehensive tests for apiKeyRepository and authController to ensure functionality.
- Updated SQLite service to create necessary tables with appropriate schema.
- Removed unused utility functions and files to clean up the codebase.
- Enhanced caddyServersStore and serverDetailsView to manage server data more effectively.
- Updated userListView to ensure user IDs are consistently treated as strings.
- Updated CORS_ORIGIN in docker-compose.yml to allow requests from http://localhost:80.
- Changed backend API access in frontend Caddyfile to proxy requests through the frontend, removing direct exposure of the backend service.
- Adjusted API base URL in configService.js to use relative path '/api/v1' instead of absolute URL.
…d-connection

Backend Proxy Integration & Simplified API Connectivity
- Replaced standard input fields with InputFieldComp in configuration, server, and user components for consistency and reusability.
- Introduced CheckboxFieldComp for checkbox inputs to streamline checkbox handling.
- Updated modal components to utilize new input and select components, enhancing maintainability.
- Improved form validation and error handling by integrating new components.
- Added new utility components: InputFieldComp, SelectFieldComp, and CheckboxFieldComp for better form management.
…t-fields

UI: improve input contrast + fix 401 → logout & redirect
chore: update dependencies in package-lock.json to latest versions
stolkie added 20 commits August 31, 2025 22:26
- Made `auditLog` prop optional in `modalAuditLogDetailsComp.vue` with a safe default.
- Added debugging watch for incoming `auditLog` payloads in `modalAuditLogDetailsComp.vue`.
- Updated `buildInfoComp.vue` layout for better spacing and responsiveness.
- Introduced new reusable components: `dashboardPanelNumberComp.vue`, `dashboardPanelTextComp.vue`, and `dashboardPanelTimelineComp.vue` for displaying various metrics and logs.
- Integrated new components into `dashboardView.vue` for a more modular and maintainable structure.
- Improved error handling in `auditLogStore.js` to gracefully handle 404 errors when fetching audit logs.
- Enhanced the dashboard's data fetching logic to ensure a smoother user experience with loading states and updates.
feat/dashboard: add dashboard, metrics + docs
chore: rename MIT license file in the project
…ontainer

feat(docker): add build dependencies and configure native module comp…
…ontainer

feat(docker): switch to glibc-based Node image and remove Alpine buil…
…ontainer

feat(docker): add .dockerignore and install build dependencies for na…
… improve error handling in configuration updates
@gitguardian
Copy link

gitguardian bot commented Sep 6, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
20239525 Triggered Username Password ff65725 backend/tests/controllers/authController.test.js View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@stolkie stolkie merged commit 52f69b6 into main Sep 7, 2025
4 of 6 checks passed
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.

2 participants