Project proposal: Self-hosted PaaS Cluster with Dokploy - #2997
Open
pspanoudakis wants to merge 4 commits into
Open
Project proposal: Self-hosted PaaS Cluster with Dokploy#2997pspanoudakis wants to merge 4 commits into
pspanoudakis wants to merge 4 commits into
Conversation
Collaborator
|
Readme is not correctly formatted Got: ['Project Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description'] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Self-hosted PaaS Cluster with Dokploy
Names and KTH ID
Deadline
Oct 11th
Category
Project
Description
We will bootstrap a small cluster of VMs (using Multipass) and set up Dokploy in cluster mode as a self-hosted PaaS. One node acts as the Dokploy leader/control-plane, and we will configure automatic registration of worker nodes so that new VMs can join the cluster and scale it horizontally without manual setup.
Our Infrastructure as Code will mostly take the form of scripts driving the Dokploy CLI (VM provisioning, cluster bootstrap, worker registration, and service deployment), and we will use ephemeral testing environments to validate that the provisioning scripts are reproducible from a clean state.
On top of the cluster we will stand up a set of core services: self-hosted CI runners, example web applications, databases, a secrets vault for credential management, and static analysis via Trivy for scanning images and dependencies for vulnerabilities. Time permitting, we would also like to add object storage, message queues, and observability (metrics/logs/tracing) as nice-to-have extensions.
Relevance
This project is directly relevant to infrastructure as code, cloud-native tooling, and CI/CD. It demonstrates how a self-hosted PaaS can be provisioned and scaled from scratch through scripted automation rather than a managed cloud provider, and it touches on horizontal scaling, secrets management, vulnerability scanning, and CI infrastructure — core building blocks of a real DevOps platform. It also highlights the tradeoffs of a CLI-scripting-based approach to IaC compared to fully declarative tools.