Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/aoepeople/typo3-cache-management
Provides management of the page caching for high traffic websites.
https://github.com/aoepeople/typo3-cache-management
cache-management typo3 typo3-extension
Last synced: about 2 months ago
JSON representation
Provides management of the page caching for high traffic websites.
- Host: GitHub
- URL: https://github.com/aoepeople/typo3-cache-management
- Owner: AOEpeople
- Created: 2016-03-11T14:12:37.000Z (almost 9 years ago)
- Default Branch: main
- Last Pushed: 2024-09-09T11:14:57.000Z (4 months ago)
- Last Synced: 2024-09-09T13:18:01.780Z (4 months ago)
- Topics: cache-management, typo3, typo3-extension
- Language: PHP
- Homepage:
- Size: 1.33 MB
- Stars: 4
- Watchers: 23
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Cache-Management for TYPO3
This is a TYPO3-Extension, that provides management of the page caching for high traffic websites.
## Download / Installation
You can download and install this extension from the [TER (TYPO3 Extension Repository)][1] or use composer.
```
$ composer require aoepeople/cachemgm
```
## Documentation
The documentation is available online at [docs.typo3.org][2].
If you want you can also render the documentation locally, this can be really helpful when adjusting
the documentation, to check before commiting.
The local rendering requires docker, and can be done like this:
```
$ source <(docker run --rm t3docs/render-documentation:latest show-shell-commands)
$ dockrun_t3rd makehtml
```
And then open `Documentation-GENERATED-temp/Result/project/0.0.0/Index.html` with your browser.
## Copyright / License
Copyright: (c) 2009 - 2024, Kasper Skaarhoj & AOE GmbH
License: GPLv3,
[1]: http://typo3.org/extensions/repository/view/cachemgm
[2]: https://docs.typo3.org/p/aoepeople/cachemgm/10.0/en-us/
## Contributing
1. Fork the repository on Github
2. Create a named feature / bugfix branch (like `feature_add_something_new` or `bugfix\thing_which_does_not_work`)
3. Write your change
4. Write tests for your change (if applicable)
5. Write documentaton for your change
6. Run the tests, ensuring they all pass
7. Submit a Pull Request using Github