Astrel Laravel Laravel Package

Product Decisions This Supports

• Environment-specific configuration without code changes: astrel_env() lets teams define named values (slugs) resolved from environment variables with sensible defaults, enabling PMs to ship features that behave differently across staging, production, or customer tiers without redeploying code.
• Feature flagging and gradual rollouts: The astrel() helper can serve as a lightweight registry for toggles and values (e.g., astrel('checkout-v2', env('CHECKOUT_V2', false))), supporting experiments and phased releases.
• Build vs. buy for config/flag management: For small-to-medium Laravel apps, this package can replace heavier third-party feature-flag services (LaunchDarkly, Unleash) when needs are simple and env-driven.
• Reducing config sprawl: Consolidates scattered env() calls into a single, testable abstraction, improving maintainability and reducing the risk of inconsistent defaults across the codebase.
• Multi-tenant or per-customer overrides: Slugs can represent tenant-specific keys, allowing PMs to pilot features with select customers via environment configuration.

When to Consider This Package

Adopt when:

• You need a minimal, Laravel-native way to resolve named values from environment variables with defaults.
• Your feature-flag or config needs are simple (boolean toggles, string/number values) and you want to avoid external dependencies.
• You value developer experience: astrel_env('my-slug') removes boilerplate compared to astrel('my-slug', env('MY_SLUG')).
• You are already using astrel() and want a cleaner path for env-backed values.

Look elsewhere when:

• You require a full-featured flag management platform with targeting rules, audit logs, percentage rollouts, or a UI for non-engineers.
• You need runtime configuration changes without deployment (this package reads env at boot; env changes typically require a restart or config cache rebuild).
• Your stack is not Laravel/PHP or you need cross-language support.
• You need strong typing, validation, or schema enforcement for configuration values.
• The package is immature for your risk profile — v1.0.x implies a young API surface; evaluate stability and maintenance cadence.

How to Pitch It (Stakeholders)

For executives: This package is a small, low-risk developer productivity tool. The new astrel_env() helper reduces boilerplate for environment-driven configuration, making it faster and safer to roll out environment-specific features and defaults. It supports lightweight feature flagging without adding a paid third-party service, keeping costs down for simple use cases. Adoption is incremental and does not require architectural changes.

For engineering: astrel_env() is a thin convenience wrapper around astrel() that automatically maps a slug to an uppercase environment variable (dashes to underscores) and supports a default value. It removes repetitive env() calls, centralizes naming conventions, and improves testability. No breaking changes in v1.0.2; the API is additive. Recommend adopting for small config/flag needs, while flagging that the package is early-stage (v1.0.x) and should be evaluated for long-term maintenance before broad rollout.