Pulse Monitor e01982c40f fix: critical auth persistence bug in Docker Quick Security Setup ...

- Docker containers were not saving credentials to persistent storage
- Non-Docker setups were saving plain text instead of hashed credentials
- After container restart, saved credentials would not work

This fixes issue #314 where users couldn't login after setting up security
in Docker containers. The Quick Security Setup now:
1. Properly hashes passwords and tokens before saving
2. Saves to /etc/pulse/.env for persistence in Docker volumes
3. Correctly loads credentials after container restart

2025-08-14 11:37:52 +00:00

..

alerts.go

attempt to address: Discord webhooks, backup types, storage duplicates, alert issues

2025-08-09 22:27:10 +00:00

auth.go

feat: enhance security and improve login UI

2025-08-13 23:07:57 +00:00

config_handlers.go

fix: reload guest metadata after import

2025-08-14 09:51:40 +00:00

diagnostics.go

fix: Docker persistence and Windows VM memory reporting

2025-08-06 16:00:22 +00:00

frontend_embed.go

feat: embed frontend in Go binary for simplified deployment

2025-08-12 12:45:57 +00:00

guest_metadata.go

fix: reload guest metadata after import

2025-08-14 09:51:40 +00:00

middleware.go

feat: Implement security, type safety, and error handling improvements

2025-07-29 17:53:51 +00:00

notifications.go

feat: add custom webhook payload templates and fix Telegram chat_id handling

2025-08-12 14:03:13 +00:00

ratelimit.go

feat: add comprehensive security system for API protection

2025-08-06 21:39:52 +00:00

router.go

fix: critical auth persistence bug in Docker Quick Security Setup

2025-08-14 11:37:52 +00:00

security.go

feat: enhance security and improve API token UX

2025-08-13 19:05:23 +00:00

settings.go

fix: ensure consistent CPU core display for all guests

2025-08-09 15:03:28 +00:00

system_settings.go

feat: enhance security and improve API token UX

2025-08-13 19:05:23 +00:00

updates.go

fix: complete update system improvements

2025-08-07 11:43:40 +00:00