逾九成(92%)公众支持室内公共场所全面禁烟
- Set APP_ENV=production and APP_DEBUG=false in .env, generate application key with php artisan key:generate, and run php artisan config:cache, route:cache, and view:cache to optimize performance. 2. Install PHP 8.1 with required extensions (OpenSSL, PDO, MBstring, etc.), configure Nginx to point to the public directory with proper server block, and set file permissions using chmod -R 755 storage bootstrap/cache and chown -R www-data:www-data on the project directory. 3. Deploy code via SFTP, Git (git pull origin main), or automated tools like Laravel Forge or GitHub Actions, then run composer install --optimize-autoloader --no-dev and php artisan migrate --force to apply database changes. 4. Schedule cron job for Laravel’s scheduler using * cd /var/www/your-laravel-app && php artisan schedule:run >> /dev/null 2>&1, and set up Supervisor with php artisan queue:work to manage queue workers. 5. Secure the app by enabling HTTPS via Certbot, monitor logs in storage/logs using tools like Sentry or Laravel Telescope, back up database and files regularly, and securely manage environment variables without committing .env to version control.
Deploying a Laravel application to production involves several critical steps to ensure your app runs securely, efficiently, and reliably. Here’s a practical guide that covers the essential tasks.

1. Prepare Your Application for Production
Before deploying, make sure your Laravel app is configured correctly for a production environment.
-
Set the environment: In your
.env
file, make sure:APP_ENV=production APP_DEBUG=false
Disabling
APP_DEBUG
prevents sensitive information from being exposed. Generate an application key:
php artisan key:generate
This ensures secure encryption of sessions and cookies.
Optimize the app: Run these commands to improve performance:
php artisan config:cache php artisan route:cache php artisan view:cache
?? Only run these in production. They can cause issues during development.
2. Set Up the Server Environment
Choose a server setup (e.g., Ubuntu with Nginx/Apache and PHP) and install the required dependencies.
Install PHP and extensions: Laravel typically requires:
- PHP >= 8.1
- OpenSSL
- PDO
- Mbstring
- Tokenizer
- XML
- Ctype
- JSON
- BCMath
- Fileinfo
- GD (for image processing)
On Ubuntu:
sudo apt install php php-cli php-fpm php-mysql php-zip php-curl php-mbstring php-xml php-bcmath php-gd php-intl
Set up a web server: Configure Nginx (or Apache) to point to your Laravel’s
public
directory.Example Nginx config:
server { listen 80; server_name yourdomain.com; root /var/www/your-laravel-app/public; index index.php; location / { try_files $uri $uri/ /index.php?$query_string; } location ~ \.php$ { fastcgi_pass unix:/var/run/php/php8.1-fpm.sock; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name; include fastcgi_params; } }
Set correct file permissions: The web server needs write access to storage and cache directories:
chmod -R 755 storage bootstrap/cache chown -R www-data:www-data /var/www/your-laravel-app
3. Deploy Your Code
There are multiple ways to deploy your Laravel app:
- Manual upload (SFTP): Suitable for small projects.
- Git-based deployment:
Push code to a private repo, then pull it on the server:
git pull origin main
- Automated deployment tools: Use tools like Laravel Forge, Envoyer, Deployer, or CI/CD pipelines (GitHub Actions, GitLab CI) for zero-downtime deployments.
After deploying the code:
Install Composer dependencies:
composer install --optimize-autoloader --no-dev
The
--no-dev
flag skips development packages.Run migrations (if needed):
php artisan migrate --force
Use
--force
in production to confirm you want to run migrations.
4. Configure Background Tasks and Scheduling
Laravel’s task scheduling and queues need proper setup.
Cron job for scheduler: Add this line to your server’s crontab (
crontab -e
):* * * * * cd /var/www/your-laravel-app && php artisan schedule:run >> /dev/null 2>&1
This runs Laravel’s scheduler every minute.
Queue workers: If using queues (e.g., Redis, database), run:
php artisan queue:work --daemon
Use process managers like Supervisor to keep the worker running:
[program:laravel-worker] command=php /var/www/your-laravel-app/artisan queue:work --sleep=3 --tries=3 autostart=true autorestart=true user=www-data
5. Secure and Monitor Your App
Use HTTPS: Set up SSL with Let’s Encrypt using Certbot:
sudo certbot --nginx -d yourdomain.com
Set up logging: Laravel logs to
storage/logs
. Monitor these files or use tools like Laravel Telescope, Sentry, or Loggly.Backup regularly: Automate backups of your database and uploaded files.
Environment-specific configuration: Never commit
.env
to version control. Store environment variables securely on the server.
Basically, deploying Laravel comes down to proper configuration, secure server setup, optimized code, and automated maintenance tasks. Get the basics right, and your app will run smoothly in production.
The above is the detailed content of How to deploy a Laravel application to production?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

There are three ways to add custom validation rules in Laravel: using closures, Rule classes, and form requests. 1. Use closures to be suitable for lightweight verification, such as preventing the user name "admin"; 2. Create Rule classes (such as ValidUsernameRule) to make complex logic clearer and maintainable; 3. Integrate multiple rules in form requests and centrally manage verification logic. At the same time, you can set prompts through custom messages methods or incoming error message arrays to improve flexibility and maintainability.

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Methods to manage database state in Laravel tests include using RefreshDatabase, selective seeding of data, careful use of transactions, and manual cleaning if necessary. 1. Use RefreshDatabasetrait to automatically migrate the database structure to ensure that each test is based on a clean database; 2. Use specific seeds to fill the necessary data and generate dynamic data in combination with the model factory; 3. Use DatabaseTransactionstrait to roll back the test changes, but pay attention to its limitations; 4. Manually truncate the table or reseed the database when it cannot be automatically cleaned. These methods are flexibly selected according to the type of test and environment to ensure the reliability and efficiency of the test.

LaravelSanctum is suitable for simple, lightweight API certifications such as SPA or mobile applications, while Passport is suitable for scenarios where full OAuth2 functionality is required. 1. Sanctum provides token-based authentication, suitable for first-party clients; 2. Passport supports complex processes such as authorization codes and client credentials, suitable for third-party developers to access; 3. Sanctum installation and configuration are simpler and maintenance costs are low; 4. Passport functions are comprehensive but configuration is complex, suitable for platforms that require fine permission control. When selecting, you should determine whether the OAuth2 feature is required based on the project requirements.

Laravel simplifies database transaction processing with built-in support. 1. Use the DB::transaction() method to automatically commit or rollback operations to ensure data integrity; 2. Support nested transactions and implement them through savepoints, but it is usually recommended to use a single transaction wrapper to avoid complexity; 3. Provide manual control methods such as beginTransaction(), commit() and rollBack(), suitable for scenarios that require more flexible processing; 4. Best practices include keeping transactions short, only using them when necessary, testing failures, and recording rollback information. Rationally choosing transaction management methods can help improve application reliability and performance.
