Coolify v5.x
# 🔥 Big news for Coolify and self-hosters! After 2 years and 400+ v4 releases, we're preparing for a stable release in 2025! However, there's one small problem. I developed version 4 pretty quickly - the first usable release was completed in a month - while I was learning Laravel as well. So the codebase is lacking; it has few tests, lacks strict rules, and lacks proper structure. It's slowing down the integration of new features, and sometimes updates break existing functionality - which is a no-go. Learning from lessons of 400+ releases and valuable feedback from the community, GitHub discussions, and Discord, we decided it was time for a complete overhaul. The past few months have been dedicated to detailed research and planning for this overhaul. But now we have time to think because: - We are profitable and growing. - I have @peaklabs-dev on my side - he has done most of the planning. 💜 🎉 Today, we’re excited to announce that the first commit to the `v5.x` branch has been made! What will be included? A lot. - A fully automated migration from v4 to v5. This is crucial. Without this, version 5 wouldn't be possible. - A total codebase refactor focused on strict PHP coding standards, maintainability, high-quality code, and a test-first approach. You might argue that I should have focused on best practices from the start, but my priority was YOLO programming to create something useful quickly. Bad practices in the codebase are the consequences. - A brand new U
Posted by andrasbacsai on Apr 24, 2025, 8:34 AM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
reliability (EdTech)
I frankly find the situation around UB puzzling.
I think it depends a little on how and where you work.
Self modifying has some sneaky failure modes with modern CPUs.
> Ban phones from class.
Coolify v5.x
Coolify v5.x
# 🔥 Big news for Coolify and self-hosters! After 2 years and 400+ v4 releases, we're preparing for a stable release in 2025! However, there's one small problem. I developed version 4 pretty quickly - the first usable release was completed in a month - while I was learning Laravel as well. So the codebase is lacking; it has few tests, lacks strict rules, and lacks proper structure. It's slowing down the integration of new features, and sometimes updates break existing functionality - which is a no-go. Learning from lessons of 400+ releases and valuable feedback from the community, GitHub discussions, and Discord, we decided it was time for a complete overhaul. The past few months have been dedicated to detailed research and planning for this overhaul. But now we have time to think because: - We are profitable and growing. - I have @peaklabs-dev on my side - he has done most of the planning. 💜 🎉 Today, we’re excited to announce that the first commit to the `v5.x` branch has been made! What will be included? A lot. - A fully automated migration from v4 to v5. This is crucial. Without this, version 5 wouldn't be possible. - A total codebase refactor focused on strict PHP coding standards, maintainability, high-quality code, and a test-first approach. You might argue that I should have focused on best practices from the start, but my priority was YOLO programming to create something useful quickly. Bad practices in the codebase are the consequences. - A brand new U
Comments (0)
No comments yet. Start the discussion.