I discovered that I had over 400k ci_session files in the writeable/session folder.
The oldest files were back from February. I checked the Session.php which had
public int $expiration = 7200;

What is causing those old session files not to be deleted ?

Geir

Today, I have run into an issue with exception handling when testing. I was building an API and wanted to take advantage of the exception handler and use exceptions to drive responses and this worked perfectly in dev or production modes. but when I wrote tests for the api endpoints, these exceptions were not being handled by the handler I registered. On digging deeper, I found out that the error handler registered by ci4 was running instead of the exception handler. To be honest, I would not consider myself an exceptional developer, so I have no telling why the error handler was firing instead of the exception handler. Is this a BUG?(current version 4.7.2)
Here is the exception handler: 

After calling software engineering 'dead,' Anthropic’s Claude Code creator Boris Cherny says coding tools like Microsoft VS Code, Apple Xcode, and others will be ‘dead soon’

Hello guys,
It seems there is no official way to place the *.env file at a different location than the projects root folder. Why?
What would be an appropriate way to load from a different location without having to overwrite Boot.php?
Thanks!
Daniel

Hi everyone,
After working with CodeIgniter 4, I wanted to share some thoughts on Dependency Injection and CodeIgniter 4:
This is not a proposal to replace CI4’s simplicity or turn it into another framework. The goal would be to modernize dependency management in a way that still respects CI4’s philosophy: simple, predictable, explicit, and lightweight.

Why Discuss This?
The current Services pattern works well and is easy to understand, but it also has some limitations for larger or more modular applications:
- Uses a service locator pattern rather than constructor injection
- Manual dependency wiring increases as projects grow
For many apps this is not a problem. But for larger projects, cleaner dependency management can be valuable.

Suggested Direction
Introduce a small optional container that can coexist with the current system.
Example:
In the bootstrap process, you can inject any class:

I've been a rabid supporter of CI since 1.7.2.  During the 'great lull' Codeigniter really took a hard hit with Laravel coming up and many devs jumping ship. I really want to do my part to help CI get back to the popularity it once had and (*gasp*) maybe rival Laravel.   

While I've been working on my CMS, I've found, what I feel, would be one of the best ways to implement such functionality similar to what Laraval offers. Their Service Providers solution to adding whatever package you want to use would be a massive advantage to Codeigniter.

The one argument I often hear/read is 'composer whatever' has this, just 'composer require' it and use it (usually coming across as kinda negative nancy since text has no real context).  I get that and it's 100% true, but that advice doesn't really cut it when CI is better than many frameworks in many ways but kinda can't get out of it's own way.  
  
As always, lively discussion is wanted, I'd really like to hear from the Foundation devs too.  Is there any interest from the Foundation to create a Service Provider/Packages and much expanded spark CLI kind of ecosystem for Codeigniter? 

Happy coding.

Hello everyone,
I have been using and loving CodeIgniter for years. I work as a developer and academic technician at a University Research Center, where we constantly build administrative and educational systems. While CI4 is blazing fast and elegantly structured, I found myself getting burned out writing the exact same CRUD controllers, HTML views, data tables, and permission logic for every new project.

To keep my sanity, I built a higher-level enterprise add-on entirely on top of CodeIgniter 4 called Ragnos. I just released it as 100% open-source and wanted to share it with the community that makes CI4 possible.

The core philosophy of Ragnos is "Configuration over Programming." Instead of writing standard MVC boilerplate for admin panels, you use our RDatasetController. You simply define a "Data Dictionary" (a plain PHP array) in your controller, and this add-on automatically renders a fully styled dashboard, handles pagination, advanced search filters, data exports, and forms.

Because it runs native CI4 under the hood, it automatically benefits from its Query Builder, CSRF protection, and XSS filtering, but it adds a dynamic Role-Based Access Control (RBAC) layer on top. Also, since modules are generated from PHP arrays, it is incredibly easy to use AI to write your configurations and generate entire modules in seconds.

You can check out the documentation, the philosophy, and the GitHub repository here: https://ragnos.build

Because the project grew quite a bit, I also wrote a complete 162-page official manual called "Ragnos from Zero to Pro" (available in English and Spanish on Leanpub) for those who want to master the architecture or implement it at an enterprise level. But the core add-on is completely free and open for the community.

I would love for the CI experts here to take a look at the code, install it, break it, and give me your honest feedback. I owe a lot to CodeIgniter, and I hope this contribution helps other developers save as much time as it has saved me.
Thanks for reading and happy coding!

I had mentioned this buried in one of my other posts.  I've had to keep claude code on a short leash because it seems to do whatever it wants. So, I had some skills for claude to use. Tonight I updated them, broke out Shield from the ci4 skill and went pretty detailed for the skills.  All free to use as cheat sheets or load up in claude (maybe other LLMs) and get something resembling what CI4 is supposed to be used for.  I'm working on a CI4 plugin too, but that's extra tokens when I have them. 

fork it, PR it, whatever you need.
https://github.com/enlivenapp/Codeignite...laude-Code

Happy Coding!

I have several modules: Main, Blog, Shop...
Each contains tests modules/src/Shop/Tests/* and data Shop/Database/{Migrations|Seeders} for them.
Errors occurred with identical tables (posts, users..) in the same test database. I am using the SQLite3 file.

How best to split the execution (random tests) without creating many connections: tests, tests_for_main, test_for_shop..? Because sometimes you may need data from modules that do not overlap.

In general, working with migrations is very strict - you can't just execute import and seeder files. And auto-searching of this data may be unsuitable: for example, when the imported data is located outside of ./Database/* or has a non-standard FQCN.

My test begin as:

I’m working on a large-scale project in CodeIgniter 4 and I want to keep my controllers as lean as possible. Currently, I’m using centralized validation in

1. Is creating a separate
   
   Code:

   app/Services
   directory the standard approach in CI4 for handling business logic?
   
2. How should I properly initialize these services? Should I use the
   
   Code:

   Services
   configuration file or just instantiate them normally in the controller?
   
3. Are there any performance overheads or architectural 'gotchas' I should be aware of when moving logic out of the controller?