tree: e4ec5da8e6d5b39cb9df1cfb82beb54e8d0f9028 [path history] [tgz]
  1. build/
  2. t3c/
  3. t3c-apply/
  4. t3c-check/
  5. t3c-check-refs/
  6. t3c-check-reload/
  7. t3c-diff/
  8. t3c-generate/
  9. t3c-preprocess/
  10. t3c-request/
  11. t3c-update/
  12. t3cutil/
  13. testing/
  14. .gitignore
  15. Makefile
  16. README.md
  17. supermicro_udev_mapper.pl
  18. traffic_ops_ort.pl
cache-config/README.md

cache-config

Traffic Control cache configuration is done via the t3c app and its ecosystem of sub-apps.

These are provided in the RPM trafficcontrol-cache-config.

To apply Traffic Control configuration and changes to caches, users will typically run t3c periodically via cron or some other system automation mechanism. See t3c.

The t3c app is an ecosystem of apps that work together, similar to git and other Linux tools. The t3c app itself has commands to proxy the other apps, as well as a mode to generate and apply the entire configuration.

Documentation

Each sub-command provides a README.md file. If your system has Pandoc and GNU make and date (UNIX date untested, might work - UNIX make definitely won't), they can also be transformed into Linux/UNIX “manual pages” using make (or explicitly make man) and reStructuredText documentation using make rst.