Announcing: One‑click access to Nightingale GUI - feedback & roadmap #163

Hi everyone, I shipped a one‑click path into the product: no signup, no form, just in. I spent the last six months building this GUI and I’d love your feedback.

Quick summary

• What it does: one‑click console access (generated SuperAdmin for local runs), in‑browser terminal and editor (code‑server), file explorer, and a minimal local stack using prebuilt multi‑arch images.
• Fast: UI is ready in under a second on local machines.
• Secure by default: synced JWT secret between frontend/backend, TLS termination for WebSocket, and secure defaults for local runs. For trusted local TLS use mkcert and drop certs into .nightingale/nginx/certs/.
• Open source: frontend/backend images are public so anyone can run or adapt it locally.

How to try (short)
Download the Nightingale-Binary

1. From the repo root:
   ./nightingale-go community setup
   ./nightingale-go community start arm # or amd
   ./nightingale-go community access # opens https://localhost

If the browser warns about the self‑signed certificate, accept the exception once (Advanced → Proceed) or use mkcert for trusted local certs.

What I’m looking for

• First impressions: UX, flow, discoverability.
• Security gaps or operational caveats for local/air‑gapped runs.
• Missing pentester workflows you’d expect out of the box.
• Platform quirks (ARM, macOS, container runtimes).

How to help / report

• Feature requests / ideas: reply here with use case + short example.
• Bugs: include steps to reproduce, OS/arch, how you ran (repo vs standalone), and docker logs output if possible.
• Contributions: PRs welcome - open an issue or a draft PR and link to this discussion.