Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Declare a clean url segment for StaticCacheFullBuildTask #145

Open
2 tasks
GuySartorelli opened this issue Sep 28, 2022 · 0 comments
Open
2 tasks

Declare a clean url segment for StaticCacheFullBuildTask #145

GuySartorelli opened this issue Sep 28, 2022 · 0 comments

Comments

@GuySartorelli
Copy link
Member

GuySartorelli commented Sep 28, 2022

The documentation indicates that the intention was for StaticCacheFullBuildTask to have a simple URL segment declared.

You can generate cache files for the entire site via the `StaticCacheFullBuildJob`.
This can either be queued up from the QueuedJobs interface or via the task
`dev/tasks/StaticCacheFullBuildTask`. This task also takes a parameter `?startAfter`
which can delay the execution of the job. The parameter should be in HHMM format,
e.g. to start after 2pm, pass `?startAfter=1400`. If it's already after the proposed
time on the current day, it will push it to the next day.
If you want to do a full site build on a cron, you should do so via the task. An
example configuration would be:
```bash
# build the cache at 1am every day
0 1 * * * www-data /path/to/sake dev/tasks/StaticCacheFullBuildTask
```

That task should have private static $segment = 'StaticCacheFullBuildTask'; added in the next major release

Acceptance criteria

  • The url segment for StaticCacheFullBuildTask is StaticCacheFullBuildTask
  • The documentation reflects the new url segment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants