New Features
🔐 Encrypted Config Export/Import
- Export entire Pulse configuration (including credentials) with passphrase encryption
- Import configurations for easy backup/restore or deployment automation
- Uses AES-256-GCM encryption with PBKDF2 key derivation (100,000 iterations)
- CLI commands:
pulse config export
andpulse config import
- API endpoints:
/api/config/export
and/api/config/import
(protected by API_TOKEN)
🐳 Docker Auto-Import
- Automatically import configuration on container startup
- Set
PULSE_CONFIG
environment variable with encrypted config - Set
PULSE_CONFIG_PASSPHRASE
for automatic decryption - Perfect for Infrastructure-as-Code and GitOps workflows
📁 Simplified Directory Structure
- Single data directory for all configuration and runtime files
- Docker:
/data
(set viaPULSE_DATA_DIR
) - Manual install:
/etc/pulse
(default) - Cleaner, more intuitive organization
Bug Fixes
- Fixed version display in Docker - VERSION file was not being included in the final Docker image
- Fixed config persistence in Docker - Configuration now correctly saves to /data directory
- Fixed service discovery - Nodes and services now properly persist and display after container restart
Improvements
- Fixed ProxmoxVE helper script to use correct environment variable
- Better Docker persistence handling
- Improved documentation for deployment scenarios
Security Note
The export/import feature uses a separate passphrase from the system encryption key, ensuring that exported configurations can only be decrypted with the correct passphrase. API endpoints require authentication via API_TOKEN to prevent unauthorized credential extraction.
Docker Images
Multi-architecture images available:
rcourtman/pulse:v4.0.3
rcourtman/pulse:4.0.3
rcourtman/pulse:4.0
rcourtman/pulse:4
rcourtman/pulse:latest
Supports: linux/amd64, linux/arm64, linux/arm/v7