https://github.com/magiclen/rocket-include-tera

This is a crate which provides macros `tera_resources_initialize!` and `tera_response!` to statically include Tera files from your Rust project and make them be the HTTP response sources quickly.
https://github.com/magiclen/rocket-include-tera

rocket template-engine tera

Last synced: 28 days ago
JSON representation

This is a crate which provides macros `tera_resources_initialize!` and `tera_response!` to statically include Tera files from your Rust project and make them be the HTTP response sources quickly.

• Host: GitHub
• URL: https://github.com/magiclen/rocket-include-tera
• Owner: magiclen
• License: mit
• Created: 2019-05-24T06:20:27.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2023-12-15T10:42:07.000Z (about 1 year ago)
• Last Synced: 2024-11-14T17:11:55.741Z (about 1 month ago)
• Topics: rocket, template-engine, tera
• Language: Rust
• Size: 55.7 KB
• Stars: 6
• Watchers: 3
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
Include Tera Templates for Rocket Framework

====================

[![CI](https://github.com/magiclen/rocket-include-tera/actions/workflows/ci.yml/badge.svg)](https://github.com/magiclen/rocket-include-tera/actions/workflows/ci.yml)

This is a crate which provides macros `tera_resources_initialize!` and `tera_response!` to statically include Tera files from your Rust project and make them be the HTTP response sources quickly.

* `tera_resources_initialize!` is used in the fairing of `TeraResponseFairing` to include Tera files into your executable binary file. You need to specify each file's name and its path relative to the directory containing the manifest of your package. In order to reduce the compilation time and allow to hot-reload templates, files are compiled into your executable binary file together, only when you are using the **release** profile.

* `tera_response!` is used for retrieving and rendering the file you input through the macro `tera_resources_initialize!` as a `TeraResponse` instance with rendered HTML. When its `respond_to` method is called, three HTTP headers, **Content-Type**, **Content-Length** and **Etag**, will be automatically added, and the rendered HTML can optionally not be minified.

* `tera_response_cache!` is used for wrapping a `TeraResponse` and its constructor, and use a **key** to cache its HTML and ETag in memory. The cache is generated only when you are using the **release** profile.

* `tera_resources_initializer!` is used for generating a fairing for tera resources.

See `examples`.

## Crates.io

https://crates.io/crates/rocket-include-tera

## Documentation

https://docs.rs/rocket-include-tera

## License

[MIT](LICENSE)