@coolify.io gets hit with 127+ low quality or straight up AI slop PRs each month. So I decided to build something to fix this and I'm excited to announce an automated solution that anyone can use which auto-close at least 98% of these PRs. Launching Saturday Feb 14!

2026 Development Log 26 🚀 Today I made more progress on the v0 implementation of many things for my upcoming product. 🛠️ Peak Projects ✅ Continued significantly refactoring and finalizing all code and most of it is now done ✅ Implemented 8 more configuration options for my product

2026 Development Log 26 🚀 Today I made more progress on the v0 implementation of many things for my upcoming product. 🛠️ Peak Projects ✅ Continued significantly refactoring and finalizing all code and most of it is now done ✅ Implemented 8 more configuration options for my product

2026 Development Log 25 🚀 It's almost time... Today I made significant progress in implementing the final initial version of all the core functionality for the first version of my project.

2026 Development Log 25 🚀 It's almost time... Today I made significant progress in implementing the final initial version of all the core functionality for the first version of my project.

tldr: jean.build - check it out! not tldr: I was so skeptical like 8 months ago about AI and AI-based workflows and now I am using it 24/7 - lol. I quickly realized that this requires a totally new kind of apps to be able to efficiently use it.

2026 Development Log 24 🚀 Today I finally figured out the final code structure and API for my upcoming product. The maintainability and naming and overall code is just chef's kiss. Cannot wait to share it with you all.

2026 Development Log 24 🚀 Today I finally figured out the final code structure and API for my upcoming product. The maintainability and naming and overall code is just chef's kiss. Cannot wait to share it with you all.

2026 Development Log 20-23 🚀 I really need to be more consistent with posting dev logs, especially also when I am not having good days as it is just not authentic always having hyper productive days. At the moment I am just not counting days that I underperformed (see total count)...

2026 Development Log 20-23 🚀 I really need to be more consistent with posting dev logs, especially also when I am not having good days as it is just not authentic always having hyper productive days. At the moment I am just not counting days that I underperformed (see total count)...

We can finally pin comments on issues. Thank you @github.com.

Cooking something extremely useful 👨‍🍳!

Cooking something extremely useful 👨‍🍳!

2026 Development Log 19 🚀 Today I reviewed and merged quite a few PRs and the Coolify repo went from 80 PRs down to 67 PRs. Also opened a long overdue PR to add official Postgres 18 support to v4. 👨‍🍳 Core Coolify Development ✅ Opened 1 PR to add official Postgres 18 and pgvector 18 support to v4

2026 Development Log 18 🚀 This is the late dev log for Monday as yesterday was a very packed day. 👨‍🍳 Core Coolify Development ✅ Completely rewrote the v5 breaking changes page and grouped the changes into high, medium and low impact breaking changes (ready for the docs)

2026 Development Log 19 🚀 Today I reviewed and merged quite a few PRs and the Coolify repo went from 80 PRs down to 67 PRs. Also opened a long overdue PR to add official Postgres 18 support to v4. 👨‍🍳 Core Coolify Development ✅ Opened 1 PR to add official Postgres 18 and pgvector 18 support to v4

2026 Development Log 18 🚀 This is the late dev log for Monday as yesterday was a very packed day. 👨‍🍳 Core Coolify Development ✅ Completely rewrote the v5 breaking changes page and grouped the changes into high, medium and low impact breaking changes (ready for the docs)

2026 Development Log 17 🚀 Today I resolved 2 v5 questions that were open for months In v5 services will no longer be an "extra thing" - they will work as securely with all settings like all other deployment types And I built a solution for knowing which v4 apps to connect to which v5 apps (image)

2026 Development Log 17 🚀 Today I resolved 2 v5 questions that were open for months In v5 services will no longer be an "extra thing" - they will work as securely with all settings like all other deployment types And I built a solution for knowing which v4 apps to connect to which v5 apps (image)

2026 Development Log 16 🚀 👨‍🍳 Core Coolify Development ✅ Ported my PHP Rust like error handling POC to a PHP package ✅ Added more methods to the package API, added tests and cleaned up file structure of the package

2026 Development Log 16 🚀 👨‍🍳 Core Coolify Development ✅ Ported my PHP Rust like error handling POC to a PHP package ✅ Added more methods to the package API, added tests and cleaned up file structure of the package

Hot take: TUIs are not it!

GitHub actions???

GitHub actions???

2026 Development Log 15 🚀 Today I finished my initial implementation of Rust/ Go like error handling for PHP. Still quite a bit more to do before it can be released but the base works now, which is the first step. Also went over 15 core Coolify PRs.

2026 Development Log 15 🚀 Today I finished my initial implementation of Rust/ Go like error handling for PHP. Still quite a bit more to do before it can be released but the base works now, which is the first step. Also went over 15 core Coolify PRs.

2026 Development Log 13 & 14 🚀 I continued on the Go/Rust inspired error handling in PHP and it is now so good already. I am now even more sure that this is the solution to error handling.

2026 Development Log 13 & 14 🚀 I continued on the Go/Rust inspired error handling in PHP and it is now so good already. I am now even more sure that this is the solution to error handling.

2026 Development Log 12 🚀 One problem I’d like to solve with v5 is error handling. It needs to be more explicit and I want to document common solutions for each error code in our docs. So today I played around with a custom, go-inspired error handling approach and I think I might be cooking.

2026 Development Log 12 🚀 One problem I’d like to solve with v5 is error handling. It needs to be more explicit and I want to document common solutions for each error code in our docs. So today I played around with a custom, go-inspired error handling approach and I think I might be cooking.

2026 Development Log 11 🚀 Another week more PRs. 80 PRs down to 64 PRs. 👨‍🍳 Core Coolify Development ✅ Merged, tested and fixed 11 PRs ✅ Merged, tested and fixed 2 Docs PRs ✅ Fixed 4+ UI issues directly on next

2026 Development Log 11 🚀 Another week more PRs. 80 PRs down to 64 PRs. 👨‍🍳 Core Coolify Development ✅ Merged, tested and fixed 11 PRs ✅ Merged, tested and fixed 2 Docs PRs ✅ Fixed 4+ UI issues directly on next

2026 Development Log 10 🚀 This is the late dev log for Friday, one of my most productive days ever with 50 contributions. I opened a docs PR that was larger than the newly released version 🤯. Also Docs PRs went from 22 to 8 open PRs.

2026 Development Log 10 🚀 This is the late dev log for Friday, one of my most productive days ever with 50 contributions. I opened a docs PR that was larger than the newly released version 🤯. Also Docs PRs went from 22 to 8 open PRs.

Bruuu Really??

Today was one of my most productive days ever 🥳 I made 50 contributions, reviewed 15 PRs and merged a big docs PR. Since my logs aren't getting much engagement, I’m postponing Log 10 to work on a new format. What would you change or do differently with my Development Logs?

Today was one of my most productive days ever 🥳 I made 50 contributions, reviewed 15 PRs and merged a big docs PR. Since my logs aren't getting much engagement, I’m postponing Log 10 to work on a new format. What would you change or do differently with my Development Logs?

We just released v4.0.0-beta.461 for @coolify.io self-hosters 🚀 This release is a big milestone towards v4 stable as it fixes 37 GitHub issues and many more bugs. It also addresses 140+ Pull Requests, adds Mattermost notification support and 18 new one-click service templates. Try it out now!

2026 Development Log 9 🚀 👨‍🍳 Core Coolify Development ✅ Finalized my service URL api PR and merged it ✅ Opened a PR that adds Mattermost notification support and merged it ✅ Added a few more fixes to my application endpoint fixes PR and merged it ✅ Fixed Docker Compose preview deployment URLs

2026 Development Log 9 🚀 👨‍🍳 Core Coolify Development ✅ Finalized my service URL api PR and merged it ✅ Opened a PR that adds Mattermost notification support and merged it ✅ Added a few more fixes to my application endpoint fixes PR and merged it ✅ Fixed Docker Compose preview deployment URLs

2026 Development Log 8 🚀 Today I went over 18 issues and 7 PRs and fixed a lot of things. 👨‍🍳 Core Coolify Development ✅ Opened part 2 of my applications API fixes with 5+ more fixes ✅ Improved my service URL update PR with better conflict checking

2026 Development Log 8 🚀 Today I went over 18 issues and 7 PRs and fixed a lot of things. 👨‍🍳 Core Coolify Development ✅ Opened part 2 of my applications API fixes with 5+ more fixes ✅ Improved my service URL update PR with better conflict checking

2026 Development Log 7 🚀 👨‍🍳 Core Coolify Development ✅ Added 5 more fixes and merged my applications API fix PR ✅ Finished the PR to add urls update functionality to services (will merge tomorrow after further testing) ✅ Tested, fixed, improved, and merged 4 PRs

2026 Development Log 7 🚀 👨‍🍳 Core Coolify Development ✅ Added 5 more fixes and merged my applications API fix PR ✅ Finished the PR to add urls update functionality to services (will merge tomorrow after further testing) ✅ Tested, fixed, improved, and merged 4 PRs

2026 Development Log 6 🚀 This week was a very productive and great start into 2026. I focused on v4 PRs and fixes. The Coolify repo went from 199 open PRs (25 new ones this week) to 81 PRs, from that I reviewed 115 PRs in just 1 week.

2026 Development Log 6 🚀 This week was a very productive and great start into 2026. I focused on v4 PRs and fixes. The Coolify repo went from 199 open PRs (25 new ones this week) to 81 PRs, from that I reviewed 115 PRs in just 1 week.

2026 Development Log 5 🚀 👨‍🍳 Core Coolify Development ✅ Investigated 5 v4 API issues and opened 2 PRs to fix them ✅ Tested, fixed, improved and merged 3 PRs ✅ Closed 5 PRs - 1 fixed differently, 3 denied, 1 slop ✅ Reviewed 1 PR for mattermost notification compatibility

2026 Development Log 5 🚀 👨‍🍳 Core Coolify Development ✅ Investigated 5 v4 API issues and opened 2 PRs to fix them ✅ Tested, fixed, improved and merged 3 PRs ✅ Closed 5 PRs - 1 fixed differently, 3 denied, 1 slop ✅ Reviewed 1 PR for mattermost notification compatibility

2026 Development Log 4 🚀 👨‍🍳 Core Coolify Development ✅ Tested, improved, fixed and merged 8 PRs ✅ Updated and enhanced the new @triggerdev.bsky.social v4 template ✅ Closed 8 PRs - 3 fixed differently, 2 stale, 1 slated for v5 refactor, 1 invalid, 1 denied

2026 Development Log 4 🚀 👨‍🍳 Core Coolify Development ✅ Tested, improved, fixed and merged 8 PRs ✅ Updated and enhanced the new @triggerdev.bsky.social v4 template ✅ Closed 8 PRs - 3 fixed differently, 2 stale, 1 slated for v5 refactor, 1 invalid, 1 denied