Hosting Laravel Package

Product Decisions This Supports

• Unified Environment Management

  • Standardize deployment tiers (production, staging, development) across all Laravel/Symfony projects, reducing inconsistencies in feature flags, logging, and monitoring.
  • Use Case: Enforce a single source of truth for environment-specific configurations (e.g., disable debug tools in production via HostingConfig::isInDevelopmentTier()).

• Observability as a First-Class Citizen

  • Automated Uptime Monitoring: Inject HTML comments for third-party tools (e.g., Pingdom) without manual template edits, improving MTTR.
  • Error Tracking: Embed TrackJS/Sentry only in non-development tiers, reducing noise in dashboards.
  • Installation-Specific Metrics: Correlate logs/metrics across microservices using the installation key (e.g., for SaaS multi-tenancy).

• Feature Flagging & Progressive Rollouts

  • Gate features by tier (e.g., enable dark mode only in staging/production) via Twig/Blade helpers like hosting_tier.
  • Roadmap: Replace scattered if (env('APP_ENV') === 'prod') checks with a centralized, maintainable system.

• Multi-Project/tenant Simplification

  • Differentiate configurations per project (e.g., analytics tokens, branding) without hardcoding, ideal for SaaS platforms.
  • Build vs. Buy: Avoid custom scripts for environment-specific logic (e.g., uptime probes, error tracking).

• Reduced Technical Debt

  • Consolidate ad-hoc hosting logic (e.g., environment checks, monitoring integrations) into a single, version-controlled package.
  • Example: Replace 50+ instances of if (config('app.debug')) with if (HostingConfig::isInDevelopmentTier()).

When to Consider This Package

• Adopt If:

  • You use Laravel/Symfony and need environment-aware configurations (e.g., feature flags, monitoring).
  • Your team manages multiple projects/tenants with shared but distinct hosting needs.
  • You want to reduce boilerplate for uptime monitoring, error tracking, or asset pipelines.
  • Your stack includes TrackJS/Sentry and you need tier-specific integration.
  • You’re building a SaaS platform requiring installation-specific metrics.

• Look Elsewhere If:

  • Your stack is not Laravel/Symfony (or you’re not using Symfony bundles).
  • You need advanced hosting features (e.g., DNS management, auto-scaling) beyond config/observability.
  • Your team prefers IaC tools (e.g., Terraform, Kubernetes) over PHP-based hosting logic.
  • You’re already using a dedicated monitoring bundle (e.g., Laravel’s spatie/laravel-monitoring) with overlapping features.
  • Your installation keys require dynamic generation (e.g., UUIDs) rather than static config.

How to Pitch It (Stakeholders)

For Executives:

"This package standardizes how we deploy and monitor our apps across environments—production, staging, development—without manual setup. Key benefits:

• Uptime monitoring is auto-integrated via HTML comments, saving DevOps time.
• Error tracking (e.g., TrackJS) is toggled per environment, keeping dashboards clean.
• Dynamic feature gating by environment reduces production risks. It’s a lightweight way to avoid reinventing hosting configuration wheels, especially as we scale to multiple projects or tenants. The tradeoff? Minimal maintenance (last updated 2023), but the core logic is simple and battle-tested."

For Engineering (Laravel/Symfony):

"The Hosting Bundle gives us:

• Centralized config for environments (tier), projects, and installations—no more scattered .env hacks.
• Twig/Blade helpers to embed monitoring scripts (e.g., TrackJS) only where needed.
• Uptime monitoring via HTML comments, compatible with tools like Pingdom.
• Symfony-native, but adaptable to Laravel via config mapping and middleware. It’s a drop-in solution for observability and environment-aware logic. Tradeoffs: Requires minor Laravel integration work (e.g., Twig → Blade), but the payoff is reduced tech debt."

For Developers:

"If you’re tired of:

• Hardcoding APP_ENV checks everywhere,
• Manually adding uptime monitor comments to HTML,
• Or forgetting to exclude dev errors from production tracking, this bundle handles it in ~10 lines of config. Just set tier, project, and installation, and you’re done. For Laravel:
• Replace HostingConfig with config('hosting').
• Use middleware to inject uptime comments.
• Swap Twig functions for Blade directives. Minimal effort, big win for consistency!"