Agnost runs on a kubernetes cluster. Whereas, as far as I know, coolify connects to your VPS and mainly use docker/docker-compose to build and deploy apps.
Hi,
This is Umit the maker of Agnost. It indeed does container building. ArgoCD and Flux are great GitOps tools that focus on automating the deployment of Kubernetes resources based on changes in a Git repository. They do not build Docker images or push them to a container registry. Instead, they deploy pre-built images to Kubernetes by syncing the state of the cluster with the manifests defined in a Git repository. On the other hand, Agnost builds and deploys images to the Kubernetes cluster and updates the image tags of your Kubernetes resources when a build and deploy pipeline is triggered.
Hi there,
This is Umit, the maker of Agnost. I think you are right it can be confusing. By container we actually mean resources such as deployments, statefulsets, cronjobs. It is not related to containers in a pod.
I am working on an open-source self hosted alternative to railway.app, render, vercel. I know there are several similar platforms as alternative to these providers but the platform I am working on will be purely running on Kubernetes clusters, no ssh to VPS and use of docker-compose or docker-swarm.
Looks interesting, does Rove also provide support for issuing TLS certificates for container services? I am also working on something similar, but it will be running on Kubernetes clusters.
Can you issue wildcard certificates with Dokku? It seems like you need to have a proxy domain to register the TXT records, since you do not know the domain of the user in advance.