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

feat/SOF-7249: take up application-flavor TS changes #62

Open
wants to merge 4 commits into
base: epic/SOF-6048
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,13 +58,13 @@ ecosystem, where `ADe` houses entity definitions for:
- `Template` - a jinja template for an application input file

The relevant data parameterizing these entities is housed in
the [Application Flavors](https://github.com/Exabyte-io/exabyte-application-flavors)
the [Application Flavors](https://github.com/Exabyte-io/application-flavors)
repository. This includes the supported applications, executables, flavors,
and defined templates.

Templates themselves are organized by application in a top-level `assets`
directory in `application-flavors` and the API for loading and working with templates can be found in
each application's `assets.js` module.
At build time, all templates are loaded and compiled into a single monolithic
JS file using `build_templates.js` so that it can be used in the client as well as in NodeJS.
TS file using `build_application_trees.ts` so that it can be used in the client as well as in NodeJS.
This is how templates are consumed from `applicaton-flavors` in `ADe`.
Loading
Loading