gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-09-25 04:33:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify Docker auth persistence via .env file

Browse Source 
Updated security documentation to explicitly mention that Docker uses
the Quick Security Setup wizard and persists credentials via /data/.env
file in the volume, making it clear how auth works in Docker deployments.
This commit is contained in:
Pulse Monitor
2025-08-14 12:47:26 +00:00
parent 75b2fad471
commit 26b6cf8fcf
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/SECURITY.md
+6 -4
View File
@@ -140,14 +140,15 @@ The easiest way to enable authentication is through the web UI:
1. Go to Settings → Security
2. Click "Enable Security Now"
3. Save the generated credentials
4. Click "Restart Pulse"
4. Click "Restart Pulse" (or restart Docker container)
This automatically:
- Generates a secure random password
- Hashes it with bcrypt (cost factor 12)
- Creates secure API token (SHA3-256 hashed)
- Configures systemd with hashed credentials
- Restarts service with authentication enabled
- For systemd: Configures systemd with hashed credentials
- For Docker: Saves to `/data/.env` with hashed credentials
- Restarts service/container with authentication enabled
#### Manual Setup (Advanced)
```bash
@@ -158,8 +159,9 @@ sudo systemctl edit pulse-backend
Environment="PULSE_AUTH_USER=admin"
Environment="PULSE_AUTH_PASS=$2a$12$..." # Use bcrypt hash, not plain text!
# Docker
# Docker (credentials persist in volume via .env file)
docker run -e PULSE_AUTH_USER=admin -e PULSE_AUTH_PASS='$2a$12$...' rcourtman/pulse:latest
# Or use Quick Security Setup and restart container
```
**Important**: Always use hashed passwords in configuration. Use the Quick Security Setup or generate bcrypt hashes manually.