Andreas Reinhold / reiniandClaude Opus 4.8
4391ad7fb9
Byproduct of the Laravel 13 upgrade: composer's post-update-cmd runs `artisan boost:update`, and Boost went 2.1.3 to 2.4.x with the update. Refreshes CLAUDE.md and boost.json for the Laravel 13 / Livewire 4 stack, updates the livewire, pest and tailwindcss skills, replaces the developing-with-fortify skill with fortify-development, and adds new laravel-best-practices and octane-development skills. Generated output, not hand-edited. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
74 lines
1.5 KiB
Markdown
74 lines
1.5 KiB
Markdown
# Configuration Best Practices
|
|
|
|
## `env()` Only in Config Files
|
|
|
|
Direct `env()` calls may return `null` when config is cached.
|
|
|
|
Incorrect:
|
|
```php
|
|
$key = env('API_KEY');
|
|
```
|
|
|
|
Correct:
|
|
```php
|
|
// config/services.php
|
|
'key' => env('API_KEY'),
|
|
|
|
// Application code
|
|
$key = config('services.key');
|
|
```
|
|
|
|
## Use Encrypted Env or External Secrets
|
|
|
|
Never store production secrets in plain `.env` files in version control.
|
|
|
|
Incorrect:
|
|
```bash
|
|
|
|
# .env committed to repo or shared in Slack
|
|
|
|
STRIPE_SECRET=sk_live_abc123
|
|
AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI
|
|
```
|
|
|
|
Correct:
|
|
```bash
|
|
php artisan env:encrypt --env=production --readable
|
|
php artisan env:decrypt --env=production
|
|
```
|
|
|
|
For cloud deployments, prefer the platform's native secret store (AWS Secrets Manager, Vault, etc.) and inject at runtime.
|
|
|
|
## Use `App::environment()` for Environment Checks
|
|
|
|
Incorrect:
|
|
```php
|
|
if (env('APP_ENV') === 'production') {
|
|
```
|
|
|
|
Correct:
|
|
```php
|
|
if (app()->isProduction()) {
|
|
// or
|
|
if (App::environment('production')) {
|
|
```
|
|
|
|
## Use Constants and Language Files
|
|
|
|
Use class constants instead of hardcoded magic strings for model states, types, and statuses.
|
|
|
|
```php
|
|
// Incorrect
|
|
return $this->type === 'normal';
|
|
|
|
// Correct
|
|
return $this->type === self::TYPE_NORMAL;
|
|
```
|
|
|
|
If the application already uses language files for localization, use `__()` for user-facing strings too. Do not introduce language files purely for English-only apps — simple string literals are fine there.
|
|
|
|
```php
|
|
// Only when lang files already exist in the project
|
|
return back()->with('message', __('app.article_added'));
|
|
```
|