Nuxt.js

Overview Managing server infrastructure shouldn't feel like a chore that distracts from writing code. Laravel Forge has long served as the gold standard for PHP developers looking to deploy applications without the overhead of manual server administration. The recent overhaul represents a fundamental shift in how developers interact with their infrastructure, moving from a personal account model to a robust, organization-centric architecture. This evolution brings Laravel developers closer to a "cloud-like" experience while maintaining the control and cost-predictability of traditional Virtual Private Servers (VPS). By automating complex tasks like zero-downtime deployments, SSL management, and server provisioning, the new Forge ecosystem allows you to focus on building features rather than debugging Nginx configurations. Prerequisites To get the most out of this guide, you should have a baseline understanding of the following: - **PHP & Laravel Basics**: Familiarity with the Laravel ecosystem and basic command-line operations. - **Version Control**: An account with GitHub, GitLab, or Bitbucket to host your repository. - **Networking Concepts**: A basic grasp of IP addresses, SSH keys, and DNS records. - **Server Fundamentals**: While Forge handles the heavy lifting, knowing what a VPS is and how it differs from shared hosting will help you make better architectural decisions. Key Libraries & Tools - **Laravel VPS**: Forge's new first-party infrastructure service powered by DigitalOcean, offering instant provisioning and integrated billing. - **Nginx**: The high-performance web server Forge configures for your sites. - **PM2**: Used specifically for the new Next.js and Nuxt.js support to manage Node.js processes. - **Let's Encrypt**: The integrated service used to provide free, automated SSL certificates. - **Redis & Meilisearch**: First-class citizens in the Forge ecosystem for caching and search functionality. Modern Organization and Team Architecture The most significant architectural change in the new Forge is the shift to Organizations. Previously, everything was tied to a personal email address. Now, the organization is the billable entity. This means you can separate your freelance projects, your agency's client work, and your personal side-hustles into distinct containers, each with its own billing and team members. Gone are the days of "Circles." They have been replaced by a proper role-based access control (RBAC) system. When you invite a team member, you can assign them specific roles like **Admin**, **Manager**, **Developer**, or **Viewer**. If the predefined roles don't fit, Forge now allows for custom roles. For example, you might want a role that can create servers but cannot delete them. This level of granularity ensures that your infrastructure remains secure even as your team grows. Additionally, SSH keys and source control providers are now linked at the organization level, meaning any team member with the right permissions can deploy to any server within that organization without needing shared credentials. Provisioning with Laravel VPS and Custom Servers James Brooks highlights the power of Laravel VPS, a managed infrastructure layer that removes the friction of connecting third-party API keys. When you choose Laravel VPS, Forge uses its private network to make servers available in roughly 10 seconds. The Site Creation Workflow Creating a site in the new Forge is a streamlined experience. You select your project type—ranging from Laravel and WordPress to the newly supported Next.js. ```bash A typical Laravel deployment script managed by Forge cd /home/forge/my-app git pull origin main composer install --no-interaction --prefer-dist --optimize-autoloader echo "" | sudo -S service php8.4-fpm reload if [ -f artisan ]; then php artisan migrate --force php artisan optimize fi ``` One major change to note: Forge no longer creates a "default" site. This was a strategic decision to encourage best practices. Previously, the default site responded to the IP address directly, which often led to configuration confusion when developers tried to rename or move it. Now, you start with a clean slate, ensuring every site on your server has a specific, intentional configuration. Zero-Downtime Deployments and Health Checks Forge has finally integrated zero-downtime deployments natively, a feature that was previously the primary reason developers used Envoyer. This works by creating a new "release" directory for every deployment. Forge clones your repository, installs dependencies, and builds your assets in this isolated directory. Only when everything is successful does it flip a symbolic link to point the web server at the new release. Implementing Health Checks To ensure your zero-downtime deployments actually work, Forge introduced integrated health checks. You can configure Forge to ping specific routes (like the default `/up` route in Laravel 11) from multiple global regions—London, New York, and Singapore—immediately after a deployment. If the site returns anything other than a `200 OK`, you get an instant notification. ```php // In a Laravel 11 application, the health check is often just a route in bootstrap/app.php ->withRouting( web: __DIR__.'/../routes/web.php', commands: __DIR__.'/../routes/console.php', health: '/up', ) ``` The Command Palette and Terminal Mastery The new Command Palette (accessible via `Cmd+K` or `Ctrl+K`) is a total workflow accelerator. It is contextually aware, meaning if you are on a server page, it prioritizes actions for that specific server. You can search for sites, create databases, or even ask the documentation questions directly within the palette. For those using Laravel VPS, the integrated terminal is a standout feature. It allows you to SSH into your server directly in the browser. Because this is a shared session, it supports collaborative debugging. If another team member joins the same server page, they can watch your terminal input in real-time, effectively enabling "pair-programming" for server administration. Syntax Notes and Conventions - **Macros**: Forge now uses macros in deployment scripts like `create_release` and `activate_release`. These are placeholders that Forge replaces with complex bash logic behind the scenes. - **Environment Variables**: Variables are hidden by default in the UI to prevent accidental "shoulder surfing" leaks. You must explicitly click to reveal them. - **Isolation**: Site isolation creates a unique Unix user for each site. This is a security best practice that prevents a vulnerability in one site (like a malicious WordPress plugin) from accessing files in another site on the same server. Practical Examples - **White-Label SaaS**: Use the new individual SSL certificate feature to manage dozens of custom domains for a single application without hitches in Let's Encrypt limits. - **Staging Environments**: Use the `onforge.com` free subdomains to instantly spin up a secure staging environment for client feedback without waiting for DNS propagation on a custom domain. - **Resource Monitoring**: Set up a server monitor to notify your Slack channel if disk space exceeds 80%, preventing database crashes due to full logs. Tips & Gotchas - **Pseudo Passwords**: Forge no longer emails these. You get one chance to download them during server provisioning. If you miss it, you'll have to reset it manually via the terminal. - **Database Types**: You can only manage one database engine (MySQL or Postgres) per server through the Forge UI. While you *can* install both via SSH, Forge will only provide UI management for the primary one selected during creation. - **VPC Networking**: When connecting a web server to a database server, use the VPC host name (e.g., `server-name.private.forge.com`) rather than the public IP. This keeps traffic within the private network, increasing both speed and security.