6c7314b86b
Made the setup and installation output more concise and reassuring for users. Less verbosity, clearer messaging. **Setup script improvements:** - Changed "Container Detection" → "Enhanced Security" - Simplified prompts: "Enable secure proxy? [Y/n]" - Cleaned up success messages: "✓ Secure proxy architecture enabled" - Removed verbose status messages (node-by-node cleanup output) - Only show essential information users need to see **install-sensor-proxy.sh improvements:** - Added --quiet flag to suppress verbose output - In quiet mode, only shows: "✓ pulse-sensor-proxy installed and running" - Full output still available when run manually - Removed redundant "Installation complete!" banners - Cleaner legacy key cleanup messaging **Result:** Users see a clean, professional installation flow that builds confidence. Technical details are hidden unless needed. Messages are clear and reassuring rather than verbose. |
||
|---|---|---|
| .. | ||
| alerts.go | ||
| auth.go | ||
| config_handlers.go | ||
| csrf_store.go | ||
| demo_middleware.go | ||
| diagnostics.go | ||
| DO_NOT_EDIT_FRONTEND_HERE.md | ||
| docker_agents.go | ||
| frontend_embed.go | ||
| guest_metadata.go | ||
| middleware.go | ||
| notifications.go | ||
| oidc_handlers.go | ||
| oidc_service.go | ||
| rate_limit_config.go | ||
| ratelimit.go | ||
| README.md | ||
| recovery_tokens.go | ||
| router.go | ||
| router_integration_test.go | ||
| security.go | ||
| security_oidc.go | ||
| security_setup_fix.go | ||
| session_store.go | ||
| settings.go | ||
| system_settings.go | ||
| types.go | ||
| updates.go | ||
Internal API Package
This directory contains the API server implementation for Pulse.
Important Note About frontend-modern/
The frontend-modern/ subdirectory that appears here is:
- AUTO-GENERATED during builds
- NOT the source code - just a build artifact
- IN .gitignore - never committed
- REQUIRED BY GO - The embed directive needs it here
Frontend Development Location
👉 Edit frontend files at: /opt/pulse/frontend-modern/src/
Why This Structure?
Go's //go:embed directive has limitations:
- Cannot use
../paths to access parent directories - Cannot follow symbolic links
- Must embed files within the Go module
This is a known Go limitation and our structure works around it.