QuickStack isn't a direct fork of Dokploy, though I can see why the UI might feel familiar - they both use the same UI component library, shadcn/ui.
The key difference lies in the underlying technology. While Dokploy (like Easypanel, Coolify, and CapRover) relies on Docker for container orchestration, QuickStack is built on k3s (a lightweight Kubernetes distribution) for orchestration, Longhorn for storage management, and Kaniko for container builds.
The key difference between Dokploy and QuickStack lies in the underlying technology. By using k3s instead of Docker for orchestration, QuickStack makes it easy to scale across multiple nodes. Additionally, with Longhorn, persistent volumes are replicated across multiple nodes instead of being tied to just one. This means that if you're running a database on VPS Node 2 and it goes offline, the database can seamlessly start on VPS Node 1 with all the data intact.
At the moment, QuickStack only supports containerized applications. You can either provide details about your Git repository (including a Dockerfile, which QuickStack will use to build the container image) or specify the name/URL of an already built container image from Docker Hub or a private registry. Here's a demo video on how deployments currently work using a git repo as source: https://youtu.be/koqGZ2ChHvw?t=183
I don’t know much about Nix yet, so I should go through the documentation first... Given QuickStack’s current setup with Kubernetes (using k3s), the platform is somewhat "tied" to containerized apps for now.
QuickStack isn't a direct fork of Dokploy, though I can see why the UI might feel familiar - they both use the same UI component library, shadcn/ui. The key difference lies in the underlying technology. While Dokploy (like Easypanel, Coolify, and CapRover) relies on Docker for container orchestration, QuickStack is built on k3s (a lightweight Kubernetes distribution) for orchestration, Longhorn for storage management, and Kaniko for container builds.
The key difference between Dokploy and QuickStack lies in the underlying technology. By using k3s instead of Docker for orchestration, QuickStack makes it easy to scale across multiple nodes. Additionally, with Longhorn, persistent volumes are replicated across multiple nodes instead of being tied to just one. This means that if you're running a database on VPS Node 2 and it goes offline, the database can seamlessly start on VPS Node 1 with all the data intact.
I hope this clears things up! :)