feat: add fastly documentation - #2430
Conversation
Developer Docs healthcheckStatus: Completed with |
📊 Documentation Impact Analyzer
Reasons
|
There was a problem hiding this comment.
Pull request overview
Adds and expands Shopware PaaS Native documentation for configuring Fastly and deploying custom VCL snippets, connecting application.yaml configuration with a dedicated snippets guide.
Changes:
- Documented
services.fastlyoptions (disable_default_snippets,snippets_path) inapplication.yaml. - Reworked/expanded the Fastly snippets page with configuration steps, required folder layout, naming rules, ordering, and validation behavior.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| products/paas/shopware/fundamentals/application-yaml.md | Adds a new services.fastly section with example configuration and option reference. |
| products/paas/shopware/cdn/fastly-snippets.md | Replaces the placeholder Fastly snippets content with a full guide covering configuration and repository layout rules. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
5325e14 to
8334c18
Compare
8334c18 to
e60542f
Compare
|
|
||
| The `FASTLY_API_KEY` and `FASTLY_SERVICE_ID` are automatically provided to the Shopware instance. | ||
| - Add your own snippets, which are deployed alongside the default ones. | ||
| - Disable the default snippets with `disable_default_snippets: true` and take full control. |
There was a problem hiding this comment.
I would write fastly.disable_default_snippets: true, since this form is used few line later.
| ``` | ||
|
|
||
| ::: warning | ||
| Snippet files in your repository are only picked up when `services.fastly.snippets_path` points at their directory. Without that option the files are ignored and never reach Fastly. |
There was a problem hiding this comment.
I would say: and never configured in Fastly instead of and never reach Fastly.
|
|
||
| ## Snippet order | ||
|
|
||
| Within a type, files are sorted by file name and the priority is assigned in that order: the first file gets priority 1 (highest), the next gets 2, and so on. |
There was a problem hiding this comment.
The priority is related to the custom snippet right? For instance the 1st snippet get priority 101 in Fastly and the 2nd 102?
|
|
||
| ```text | ||
| config/fastly/recv/ | ||
| ├── 001-auth.vcl # priority 1 |
There was a problem hiding this comment.
I think here you should show a real example of a file including storefront and cdn.
I'm also a bit confused about the prefix, what should be the order?
001-storefront-foo.vcl
storefront-001-foo.vcl
Summary
Related links
Checklist
PageRefreferences where relevant..gitbook.yamlif pages were moved, renamed, or deleted..wordlist.txt(and sorted it) if spellcheck flags new legitimate terms.Notes