Skip to content

Commit a8f5044

Browse files
committed
Update README.md
1 parent 19f51a9 commit a8f5044

1 file changed

Lines changed: 5 additions & 3 deletions

File tree

README.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,16 @@
11
# Deploy Laravel
22
Production-ready zero-downtime deployment script for Laravel.
33

4+
Also check out [Lit](https://github.com/SjorsO/lit) for deployments from the CLI.
5+
46
## Install
5-
Visit the link below for the download and the installation guide:
7+
Visit the links below for the download and the installation guide:
68
- [Deploy Laravel for GitHub Actions](https://sjorso.com/deploy-laravel/github/step-1)
79
- [Deploy Laravel for GitLab CI/CD](https://sjorso.com/deploy-laravel/gitlab/step-1)
810
- [Deploy Laravel for Bitbucket Pipelines](https://sjorso.com/deploy-laravel/bitbucket/step-1)
911

1012
Requirements:
11-
- Laravel 5 or higher
13+
- Laravel 5 up to 12
1214
- Ubuntu 16.04 or higher / CentOS7 or higher
1315

1416
Installing this deployment script can typically be done in less than 10 minutes.
@@ -34,7 +36,7 @@ A quick overview:
3436

3537
## Zero-downtime deployments (current & releases directory)
3638
This deployment script is zero-downtime, this has two big advantages: deployments don't cause downtime for your users, and deployments are gracefully aborted when something goes wrong.
37-
To understand what exactly this means, lets first look at what it means if your deployments are not zero-downtime.
39+
To understand what exactly this means, let's first look at what it means if your deployments are not zero-downtime.
3840

3941
A typical not zero-downtime deployment strategy is SSHing into your server, calling `git clone`, and then running `composer install`.
4042
While these commands are running your application is in limbo: some code is new, some code is old, and some new dependencies are missing entirely.

0 commit comments

Comments
 (0)