pack
coolify
Our great sponsors
pack | coolify | |
---|---|---|
46 | 109 | |
2,373 | 11,798 | |
2.0% | 12.0% | |
9.5 | 10.0 | |
1 day ago | about 19 hours ago | |
Go | PHP | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pack
- Différentes façons de déployer une application front faites en JS
-
K8s powered Git push deployments
I've recently found this quote by Kelsey Hightower:
"I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."
Source: https://twitter.com/kelseyhightower/status/85193508753294540...
In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.
My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.
Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?
Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.
Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?
-
Crafting container images without Dockerfiles
Although Dockerfiles have the benefit of migrating existing workloads to containers without having to update your toolchain, I definitely prefer the container-first workflow. Cloud Native [Buildpacks](https://buildpacks.io/) are a CNCF incubating project but were proven at Heroku. Buildpacks support common languages, but working on a Go project I've also had a great experience with [ko](https://ko.build/). Free yourself from Dockerfile!
-
Kubero : alternative à Heroku pour Kubernetes …
Cloud Native Buildpacks
-
The world outside of WordPress
It's big and overwhelming and sometimes scary. But you know what? It's also fun, engaging, and very refreshing. Because I'm a DevRel, I don't have many chances to focus on something particular. Still, I'm having a lot of fun exploring different CMSs (like Statamic, Craft, or Sanity), new approaches (at last, I understood why the headless approach is so important), and diving into tech I never used before (hello Buildpacks).
- Does anyone use any alternatives to Dockerfile for creating containers? Something with nicer syntax?
- Jetstack Paranoia: A New Open-Source Tool for Container Image Security
-
YAML Buildpack: Auto Validate Configuration Repositories
[5] https://buildpacks.io/
-
Devbox 📦 : Instant, easy, and predictable shells and containers
Devbox analyzes your source code and instantly turns it into an OCI-compliant image that can be deployed to any cloud. The image is optimized for speed, size, security and caching ... and without needing to write a Dockerfile. And unlike buildpacks, it does it quickly.
-
A selfhosted Heroku clone on your Kubernetes cluster
I had a short look into buildpacks.io . So I don't have a firm opinion yet. But as much i understand now, it really builds Container images. Kubero goes a different approach. The buildstep only compiles the project to a mounted volume, which is mounted readonly to the running container. Further more is the detection step unnecessary, since the dev knows what he wants to build and selects the buildimage. How ever, I'm still looking into it, so see if my project can profit from the great work there in any other way.
coolify
-
Let's build a screenshot API
Heroku and similar providers can simplify the server management issues, but you can use something much better that can combine both cost efficiency and ease of deployment—Coolify:
-
Quantum alternatives - coolify and meli
3 projects | 12 Mar 2024
-
Serverless Horrors
The creator of the blog is Andres who is also building coolify[0], a heroku/netflify self-hosted alternative. I wanted to give a shoutout to him and his product. I've been running it for a few months and love it. Really was has been kinda the secret sauce of ease of use for me to start self-hosting things like changedetector, jdownloader, vaultwarden, etc.
It also has a pretty nicely growing community where people are contributing new templates (I added one for Syncthing) and helping each other debug.
The only issue I've had with it is things kinda fall over if you run out of disk space, which happened when I was running on an instance with just 10GB storage. So a little better alerting or prevention around that would be great but otherwise it has been pretty solid.
> VPSs being “easy to manage” is a strong option full of assumptions.
There are definitely many footguns with managing a VPS but I think the threshold to get vaguely competent with a VPS is not really that far off with getting familiar with the average cloud platform - which comes with its own dangers, like the near-total inability to put an upward cap on fees that that person found out with Netlify recently.
Having a $5 VPS and knowing it's never going to cost your more than $5 might balance out a lot of things on the other side for a lot of people.
(And, as a bonus, it comes with the benefit of having a better idea of what is going on on the actual computer which is running your code.)
Platforms like https://coolify.io/ (which I have not tried, but looks interesting) seem to give you some of the abstractions that you get in cloud platforms to save you having to mess with too much low level stuff and become an expert in a billion separate systems.
If you have Debian with automatic updates that does most of the heavy lifting for you. The hardest problem I have is resisting the temptation to just install everything, because the cost to do it is capped at my VPS monthly fee.
So yep, it comes with a lot of assumptions. But so does everything!
-
Netlify just sent me a $104K bill for a simple static site
https://coolify.io/ might be worth a look
Hetzner or DigitalOcean with Coolify [0] works great, it's like an open source Heroku that runs on any host, you get git push to deploy, and a bunch of other features built in. It only works on one machine at a time though so it's not like a CDN but for small sites, it's great.
-
The 2024 Web Hosting Report
The modern iteration of these tools has taken the developer experience learnings from the Platform as a Service (PaaS) category, and will bring them to your own VM, giving you your own personal PaaS. Example of this include Dokku, Coolify, Caprover, Cloud66 and many more!
- Best image optimization alternative to Vercel
-
Working on Multiple Web Projects with Docker Compose and Traefik
I believe this is the core of what Coolify[0] does.
-
Contributing to Tech Communities: How Open-Source can land you a job and get you out of the Skill Paradox 💼
Coolify
What are some alternatives?
CapRover - Scalable PaaS (automated Docker+nginx) - aka Heroku on Steroids
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
porter - Kubernetes powered PaaS that runs in your own cloud.
kaniko - Build Container Images In Kubernetes
helm-charts - Prometheus community Helm charts
jib - 🏗 Build container images for your Java applications.
meli - Platform for deploying static sites and frontend applications easily. Automatic SSL, deploy previews, reverse proxy, and more.
Empire - Empire is a PowerShell and Python post-exploitation agent.
buku - :bookmark: Personal mini-web in text
infrastructure - Infrastructure files for coolLabs
SvelteKit - web development, streamlined
dokku-toolbelt - Toolbelt for dokku, similar to the heroku toolbelt