-
-
Notifications
You must be signed in to change notification settings - Fork 28
v0.0.2 - SQLite is here! #55
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.
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
Conversation
…istent feat: Update API routes to include versioning and adjust Swagger docu…
…for security reasons
…file for security reasons
…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.
…configuration details
…gine Add SQLite Database Engine Support
- 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
Integrate alternative JSON editor
- 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
- 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.
…proved API key handling
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…
…tive module compilation
…ontainer feat(docker): add .dockerignore and install build dependencies for na…
…on, fix bug with validation of content
… improve error handling in configuration updates
…s history retrieval with filtering options
Fix/applying configs
|
| 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
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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.
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