mirror of
https://github.com/bitinflow/bunny-cli.git
synced 2026-03-13 13:45:54 +00:00
Remove phar updater
This commit is contained in:
10
README.md
10
README.md
@@ -14,6 +14,12 @@ To install Bunny CLI, you need to be using Composer. For more details about Comp
|
||||
composer global require own3d/bunny-cli
|
||||
```
|
||||
|
||||
If you want to update the Bunny CLI, just execute the following command:
|
||||
|
||||
```bash
|
||||
composer global update own3d/bunny-cli
|
||||
```
|
||||
|
||||
Bunny CLI currently only comes with a `deploy` command. With this command, you can easily synconizise your `dist` folder with your edge storage.
|
||||
|
||||
> **IMPORTANT**: All files in the edge storage that are **not** in your local `dist` directory will be deleted.
|
||||
@@ -49,6 +55,10 @@ We offer you a [GitHub Action for Bunny CLI](https://github.com/marketplace/acti
|
||||
args: deploy --dir=dist
|
||||
```
|
||||
|
||||
## Environment Variables
|
||||
|
||||
|
||||
|
||||
## Secure your `.well-known/bunny-cli.lock` file
|
||||
|
||||
Bunny CLI generates a lock file, which by default is located at `.well-known/bunny-cli.lock`. This file locks the files of your project to a known state. To prevent this from being publicly accessible it is recommended to create a new edge rule in your pull zone. You can use the following example as a template:
|
||||
|
||||
Reference in New Issue
Block a user