general

Standard Laravel conventions dictate using the config() helper for reading values in application code. You should avoid using env() outside of configuration files to prevent runtime environment leakage and ensure consistent configuration access across your project.

To implement structured logging in Laravel, use the Log facade with context arrays to record meaningful event data. For tracking business model actions, apply Spatie Activity Log to consistently log user activity and model changes across your application.

Yes, you can enforce Laravel coding standards automatically by integrating Laravel Pint for style checks and static analyzers for quality validation. These tools inspect models, controllers, and services to validate that your codebase follows unified project-wide conventions.

You should not use env() in Laravel application code outside of config files because it returns null after configuration caching. Relying on env() in controllers or models causes runtime environment leakage, so always use config() to access environment variables.

Yes, these Laravel conventions are applicable to projects of any size. They guide models, controllers, migrations, services, and utilities to follow a unified standard, ensuring that both small setups and large teams maintain a uniform codebase.

The best way to manage multi-step database writes in Laravel is using DB::transaction(). Wrapping Eloquent or Query Builder operations in DB::transaction() ensures that all database changes roll back automatically if any step fails, maintaining data integrity.