You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-1Lines changed: 20 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -239,4 +239,23 @@ You can verify Fileset server is working as you expect by looking for the follow
239
239
| `x-fileset-site` | The site being served. Usually this will be `default` but for multi-site installations, this will be useful for determining which site is serving. |
240
240
| `x-fileset-ref` | The Git commit sha that corresponds to the serving manifest that is handling your request. |
241
241
| `x-fileset-blob` | The blob directory key corresponding to the file being served. This is the SHA-1 hash of the file's content. |
242
-
| `x-fileset-ttl` | For scheduled deployments, the value of this header will correspond to the timestamp for the timed deployment being served. |
242
+
| `x-fileset-ttl` | For scheduled deployments, the value of this header will correspond to the timestamp for the timed deployment being served. |
243
+
244
+
## Tips
245
+
246
+
### Usage within Makefile
247
+
248
+
The absolute path to the `fileset` executable must be specified to invoke the CLI.
249
+
250
+
```
251
+
./node_modules/.bin/fileset upload build
252
+
```
253
+
254
+
### Usage with Grow.dev
255
+
256
+
First, build the site to the `build` directory. Then, upload the directory to Fileset.
0 commit comments