CI/CD: fixture jobs (no staging job, FIXTURES_PURGE, cache flush after every load)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, gitlab, markdown
- Domain
- ci-cd, documentation
Research direction
Start with content/6.deployment/3.ci-cd.md and compare it with components-web-app commit c06c04c and MR !11. Search the documentation for pages describing fixture loading, then update the job list, FIXTURES_PURGE behavior, and post-load cache flushing; done means all relevant pages match the GitLab and GitHub behavior described in the issue.
Written by the indexing model from the issue text.
Description
components-web-app c06c04c (MR !11) changes how fixture jobs work. content/6.deployment/3.ci-cd.md needs updating, along with any page about loading fixtures.
-
Staging has no fixture job any more, on GitLab or GitHub. Staging runs under the production environment and shares production's database, so a fixture load there would write to production. Remove
load fixtures stagingfrom the job list. -
FIXTURES_PURGE(a new CI variable, default"false") makes a fixture job empty the database before loading, so a changed scaffold can be reloaded:- review apps:
"true"(or"force"); - production: only
"force"."true"prints a notice and appends.
Only the fixture job reads it, never a deploy or pod start. On GitHub, the fixture step runs after every deploy while
ENABLE_DATABASE_FIXTURESis set, so with both set, every review deploy (or manual production run) purges. - review apps:
-
Every fixture load ends by flushing the whole HTTP cache (
silverback:api-components:purge-http-cache), so reloaded content isn't served stale from Souin. -
Appending is still the default, and it still stops at the first existing route on a seeded database. Making appends idempotent is api-components-bundle#319.
- Dominant language
- Vue
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from components-web-app/docs
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
components-web-app/docs#119 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
components-web-app/docs#1 · 2 comments ·
All issues in components-web-app/docs
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area/cli kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
alunduil/zfs-replicate#730 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
infrastructure
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
alunduil/siren-json.hs#232 ·
Maintainers usually reply within 1 day