5 Commits

Include renames

Author	SHA1	Message	Date
Paul NothaftandPaul Nothaft	0e459b3293	docs: define security support across stable and main (#1351) ... Co-authored-by: Paul Nothaft <[email protected]>	2026-09-08 08:32:54 +02:00
Paul Nothaft	0205c7dcce	chore: migrate Docker registry + GitHub URLs to PicPeak org ... Repo transferred from the-luap/picpeak → PicPeak/picpeak. Docker images publish to ghcr.io/picpeak/picpeak/{backend,frontend} (lowercase, per the GHCR canonical form computed by docker-build.yml's `${GITHUB_REPOSITORY,,}`). Sweep covers: - docker-compose.production.yml + Dockerfiles → new image registry path - README, CONTRIBUTING, SECURITY, SIMPLE_SETUP, scripts/picpeak-setup.sh → new GitHub URLs - Update-check / release-notes services (updateCheckService, environmentService, updateNotificationService, adminSystem, UpdateNotification, githubReleaseUrl) → GitHub API + tag URLs use the canonical PicPeak/picpeak path - Issue templates + README-DOCKER + workflow README → updated package URLs - One commit-context comment in migrations/090 + customerAccountsService CHANGELOG.md is intentionally untouched (historical release entries are immutable; GitHub auto-redirects the old URLs indefinitely). CLAUDE.md keeps the bare `(the-luap)` reference — that's the maintainer's personal handle, not a repo URL. 22 files, 48/48 line swaps (every change is a 1:1 URL replacement).	2026-06-29 20:20:13 +02:00
Paul Nothaft	67b0f32456	fix: update security policy with proper contact email and private reporting ... - Replace placeholder [email protected] with [email protected] - Add GitHub Private Vulnerability Reporting links - Update supported versions table to 2.x.x Closes #223	2026-03-11 20:21:32 +01:00
paul	0c989ce086	docs: replace email addresses with GitHub issue links ... - Remove all @example.com email addresses from documentation - Replace [email protected] with GitHub security issue links - Replace [email protected] with GitHub issue link - Update CONTRIBUTING.md to use GitHub issues instead of email - Ensure all communication happens through GitHub's issue tracking system - Avoid direct email communication for better transparency and tracking	2025-07-24 21:28:44 +02:00
paulandClaude	1773ed5f95	Initial commit - Project start (July 17, 2025) ... Original: feat: enhance security logging and ensure rate limit blocks are properly tracked - Add comprehensive logging for rate limit blocks with full request details - IP address (with proper proxy detection), user agent, headers, timestamps - Rate limit info (current count, limit, remaining, reset time) - Separate tracking for auth vs general endpoints - Enhance authentication failure logging - JWT validation failures with detailed error info - Admin auth attempts without token - Failed token validation with user context - All events include IP, path, method, user agent - Improve Winston logger configuration for production - Add automatic log rotation (10MB errors, 50MB combined) - Create separate security.log for auth/rate limit events - Ensure logs directory exists automatically - Add structured JSON format for log aggregation - Support container logging with LOG_TO_CONSOLE env var - Create comprehensive documentation - Security logging guide with examples - Monitoring recommendations - Configuration reference - Add test script to verify logging functionality All rate limit settings remain configurable via admin panel: - Window duration, max requests, auth limits - Skip authenticated requests option - Public endpoints only option 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>	2025-07-24 16:57:07 +02:00