bitinflow/bunny-cli
1
0
Fork 0
mirror of https://github.com/bitinflow/bunny-cli.git synced 2026-03-13 13:45:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Improve lock file

Browse Source
This commit is contained in:
René Preuß
2021-07-22 17:28:09 +02:00
parent 820287dd2c
commit 4b9e117f1a
8 changed files with 105 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -10,7 +10,7 @@ With Bunny CDN's Storage Edge, your web applications benefit from replicated sto
Bunny CLI currently only comes with a `deploy` command. With this command, you can easily synconizise your `dist` folder with your edge storage.
> All files in the edge storage that are **not** in your local `dist` directory will be deleted.
> **IMPORTANT**: All files in the edge storage that are **not** in your local `dist` directory will be deleted.
```plain
➜ $ bunny deploy
@@ -43,6 +43,16 @@ We offer you a [GitHub Action for Bunny CLI](https://github.com/marketplace/acti
args: deploy --dir=dist
```
## 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:
Action: `Block Request`
Condition Matching: `Match Any`
Condition: If `Request URL` `Match Any` `*/.well-known/bunny-cli.lock`
Now the file should no longer be accessible. It can take a few minutes until your Edge Rule is active.
## Frequently Asked Questions
### Q: Is this a zero-downtime deployment?