Original Summary

Hey everyone, In smaller teams or client agencies, setting up full CI/CD pipelines (GitHub Actions, Jenkins, etc.) can sometimes feel like overkill for simple staging servers. In my experience, devs often resort to manually SSHing into servers, running git pull, and triggering builds manually—which is slow and error-prone. I'm currently building an open-source, 1-click deployment dashboard to automate this workflow as a side project, and wanted to get some feedback on the architecture. The Current Architecture: Backend: Node.js, Express, PostgreSQL, Apache Kafka (KRaft mode) Frontend: Next.js, Tailwind CSS Worker: node-ssh for remote execution What's working so far: Multi-user setup with HttpOnly JWT auth Adding servers with custom SSH credentials (password or private key) Event-driven Kafka workers that SSH into servers and run build scripts Dynamic workspace setup (creates folders and syncs code) Up next: Switching from short-polling to WebSockets (Socket.io) for real-time terminal log streaming from the worker to the dashboard. For those managing smaller infrastructure setups: How do you handle quick deployments without over-engineering your pipeline? Would love to hear thoughts on using Kafka/workers for remote SSH execution vs. other lightweight patterns. (P.S. I am the sole developer building this side project to learn event-driven architectures. Happy to drop the repo link in the comments if anyone wants to look at the code!)   submitted by   /u/Repulsive-Bicycle969 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/21 01:47:01