engine_static_save
Save an existing static CSS or JS file, either by providing content or a file path. Optionally include it in a bundle and raise the build number to force browsers to load the updated file.
Instructions
Save an existing static file (css/js). The body comes either as content, or as file - a path on this machine, and then it travels byte for byte.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | No | Path on this machine, absolute or off the store folder; instead of content. | |
| path | Yes | ||
| build | No | Raise the build number of the store. The page hangs that number on its css and js, so a browser keeps the file it already has until the number grows - which means a saved style reaches nobody without this. Say it when the change is meant for the visitors, and mind that every visitor then fetches the styles anew once. | |
| bundle | No | The builds this file goes into. Given, it is written whole and the builds of the template are reassembled at once; omitted, the file keeps what it had. Both fields empty takes the file out of every build. Load the file first - the answer says what stands there now. | |
| content | No |