tonyair/silverstripe-staticpublisher
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-staticpublisher synced 2024-10-22 14:05:54 +02:00
Code Issues Projects Releases Wiki Activity

Update buildcache url in documentation (Fixes: #23)

Browse Source
This commit is contained in:
Will Rossiter 2013-09-16 19:49:30 +12:00
parent bacc1d44ba
commit 00e49ccd19
2 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
_config/routes.yml Normal file
View File

@ -0,0 +1,6 @@
---
Name: staticpublisherroutes
---
Director:
rules:
'dev/buildcache': '->dev/tasks/RebuildStaticCacheTask'

8
docs/en/StaticPublisher.md
View File

@ -449,20 +449,20 @@ you can build the static HTML files. This is done by the `RebuildStaticCacheTask
Execution via URL
```
http://www.yoursite.com/dev/buildcache?flush=1
http://www.yoursite.com/dev/tasks/RebuildStaticCacheTask?flush=1
```
Execution on CLI (via [sake](framework/en/topics/commandline))
```
sake dev/buildcache flush=1
sake dev/tasks/RebuildStaticCacheTask flush=1
```
Depending on which extension you've set up for your `SiteTree` (`FilesystemPublisher`
or `RsyncMultiHostPublisher`), the method `publishPages()` either stores the generated
HTML-files on the server's filesystem, or deploys them to other servers via rsync.
It is advisable to set `dev/buildcache` up as an automated task (e.g. unix cron)
which continually rebuilds and redeploys the cache.
It is advisable to set `dev/tasks/RebuildStaticCacheTask` up as an automated
task (e.g. unix cron) which continually rebuilds and redeploys the cache.
## Related