🔥 Ignite

Zero to production-ready Laravel in under 5 minutes

Ignite is the fastest way to launch battle-tested Laravel environments on AWS EC2.
One command. Full stack. Zero config.

Get Started »

_{Built with precision by SystemPath}

Ignite isn't just another provisioning script. It's a complete, production-grade Laravel development environment that deploys in minutes—not hours.

• 🚀 One-Command Deploy – Paste a single line into EC2 user data and walk away
• 🏗️ Battle-Tested Stack – Laravel 11, Inertia, React, PostgreSQL 17, Redis, Nginx
• 🔐 Security First – SSH hardening, UFW firewall, Fail2ban, automatic SSL with Let's Encrypt
• 🛠️ 20+ Helper Commands – deploy, fresh, vdev, and more for instant productivity
• 📦 Smart Package Selection – Stripe, AWS SDK, Spatie suite, TypeScript transformers—pre-configured
• 🎯 Modular & Hackable – Don't like our choices? Fork it, customize it, rebuild it

Paste this as User Data when launching an Ubuntu EC2 instance:

#!/bin/bash
curl -fsSL https://raw.githubusercontent.com/systempath/ignite/main/dist/ec2-userdata.sh | bash

That's it. SSH in 5 minutes later to a fully configured Laravel environment.

Already have an Ubuntu server? Run this:

curl -fsSL https://raw.githubusercontent.com/systempath/ignite/main/dist/ec2-userdata.sh | sudo bash

Want to tweak the stack? Fork and modify:

git clone https://github.com/systempath/ignite.git
cd ignite
# Edit config/variables.sh or modules/ as needed
bin/build-userdata
# Deploy your custom dist/ec2-userdata.sh

• UFW Firewall – Ports 22, 80, 443, 8025, 8080 only
• Fail2ban – Automatic SSH intrusion prevention
• SSH Hardening – Key-only auth, no root login
• Let's Encrypt – Automatic SSL with setup-ssl command
• Claude Code CLI – AI-powered development assistant

• deploy – Full deployment pipeline (migrate, build, optimize)
• fresh – Quick rebuild without migrations
• vdev – Start Vite dev server with HMR
• gkey – Display GitHub deploy key
• setup-ssl – Configure Let's Encrypt SSL
• backup-database – Manual PostgreSQL backup
• tscope – Laravel Telescope dashboard info
• mailpit – Email testing interface info

When you run setup-laravel, you get a complete Laravel 11 application with:

Ignite uses a modular build system that compiles separate components into a single deployment script:

ignite/
├── modules/        # Ordered setup phases (00-system-prep → 999-finalize)
├── templates/      # Config files & helper scripts (base64-encoded)
├── config/         # Version defaults & build utilities
├── bin/            # Build script
└── dist/           # Generated ec2-userdata.sh (don't edit directly)

Key principle: Edit sources in modules/ and templates/, never the generated dist/ file.

Contributing or customizing? Follow this workflow:

1. Edit – Modify modules in modules/ or files in templates/
2. Build – Run bin/build-userdata to regenerate dist/ec2-userdata.sh
3. Validate – Syntax check with bash -n dist/ec2-userdata.sh
4. Test – Deploy to disposable EC2, monitor /var/log/userdata.log
5. Commit – Commit source changes, not generated files

export PHP_VERSION=8.3
export NODE_VERSION=20
export POSTGRES_VERSION=16
export LARAVEL_AUTO_SETUP=false  # Skip automatic Laravel setup
bin/build-userdata

export USERDATA_URL="https://your-domain.com/custom-userdata.sh"
curl -fsSL https://raw.githubusercontent.com/systempath/ignite/main/aws-ec2-user-data-downloader.sh | bash

• ⛔ Never run locally – Script assumes Ubuntu EC2 with root privileges
• 📝 Commit sources only – Commit changes to modules/ and templates/, not dist/
• 🔑 Git setup – Run gkey after provisioning to configure git identity
• 📚 Learn the helpers – Run server-help or shelp to see all available commands
• 🔍 Monitor setup – Watch progress with tail -f /var/log/userdata.log

Found a bug? Have a feature request? Open an issue.

Want to contribute? PRs welcome! Please read our development workflow above.