Download the PHP package albertoarena/laravel-netsons-deploy without Composer

Laravel Netsons Deploy

Deploy Laravel applications to Netsons shared hosting (cPanel, SSD plans) via GitHub Actions, supporting both FTP upload and SSH/git-clone strategies.

Features

• Two deployment strategies: FTP (incremental sync) and Git (server-side clone)
• Release-based deployments with timestamped directories
• Zero-downtime release switching via proxy index.php
• Shared .env and storage/ across releases
• Automatic cache clearing and rebuilding (with dependency caching for faster builds)
• Database migrations on deploy
• Automatic key:generate and seeder support on first deploy (auto-detects spatie/laravel-permission)
• Auto-detect env variables from .env.example (secret-backed and static, with editable values)
• Custom .env variable management (secret-backed and static values)
• Build environment variables (e.g., Vite config)
• Custom post-deploy artisan commands
• Envaudit .env validation (opt-in, default enabled)
• Slack deploy notifications (opt-in)
• .htaccess management for root and public directories
• Configurable FTP root path for different account setups
• Configurable release retention (prune old releases)
• SSH retry resilience (automatic retry on connection timeouts, configurable attempts/delay/timeout)
• SSH cleanup after every deploy
• Works with Netsons SSH (port 65100) and cPanel PHP (ea-phpXX)

Quick Start

1. Install the package

2. Run the installer

This will:

• Guide you through strategy selection (FTP or Git)
• Publish the config file to config/netsons-deploy.php
• Generate .github/workflows/deploy.yml with your settings
• Show the required GitHub Secrets and Variables

3. Configure environment variables

Add secret-backed variables (e.g., DB_PASSWORD), static values (e.g., SESSION_DRIVER=database), or build variables (e.g., VITE_APP_NAME).

4. Configure GitHub Secrets

Add the required secrets to your GitHub repository (Settings > Secrets and variables > Actions). See GitHub Secrets Reference.

5. Deploy

Trigger the workflow from GitHub Actions > Deploy to Netsons > Run workflow.

Strategy Comparison

Private repos with Git strategy: Set GIT_REPO to the HTTPS URL and configure GIT_TOKEN. For same-repo deploys, use ${{ github.token }}. See Private Repository Setup.

Usage as a Reusable GitHub Action

You can also use this as a reusable action in your workflow:

See action.yml for all available inputs.

Artisan Commands

netsons:install

Interactive setup wizard. Publishes config and deploy workflow, shows required secrets/variables.

netsons:check

Shows your local configuration, checks that the workflow file exists, and lists required GitHub Secrets/Variables.

netsons:env

Manage custom environment variables for deployment without editing the workflow manually.

Variable types:

• Secret-backed — values from GitHub Secrets (e.g., DB_PASSWORD)
• Static — fixed values (e.g., SESSION_DRIVER=database)
• Build — available during asset build (e.g., VITE_APP_NAME)

After adding/removing variables, regenerate the workflow:

The installer will prompt you to overwrite the existing workflow. Use --force to skip confirmation prompts.

Configuration

The config file config/netsons-deploy.php covers:

• Strategy — ftp or git
• SSH — host, port (default 65100), user, retry settings (retries, delay, timeout)
• PHP binary — remote path (default /usr/local/bin/ea-php84)
• Deploy path — remote directory (default public_html)
• FTP — host, port, user, password, protocol, root path
• Git — repo URL, branch
• Releases — number to keep (default 5)
• Post-deploy — toggle migrations, cache rebuilding, queue restart
• Seeders — classes to run on first deploy

The netsons-deploy.json file manages:

• Secret-backed env vars — mapped to GitHub Secrets
• Static env vars — fixed values per deployment
• Build env vars — available during asset build
• Custom commands — extra artisan commands for post-deploy
• Seeders — classes to run on first deploy only (auto-detected from composer.json)
• Notifications — Slack webhook for deploy alerts

See Configuration Reference for details.

Documentation

• Configuration Reference
• FTP Strategy Guide
• Git Strategy Guide
• Netsons Setup Guide
• GitHub Secrets Reference
• Troubleshooting

Requirements

• PHP 8.2+
• Laravel 10, 11, 12, or 13
• GitHub Actions
• Netsons shared hosting (cPanel, SSD plans)

Contributing

Contributions are welcome! Please open an issue or submit a pull request.

1. Fork the repository
2. Create your feature branch (git checkout -b feature/my-feature)
3. Write tests for your changes
4. Ensure all tests pass (composer test)
5. Commit your changes
6. Push to the branch
7. Open a pull request

License

MIT License. See LICENSE for details.