Shared Assets
Overview
Section titled “Overview”assets.lef.software serves standard, reusable, deterministic datasets and icons used by LEF software projects.
Datasets
Section titled “Datasets”JSON payloads are served from the /data/ prefix. When using the dedicated data host, URLs look like:
- https://data.lef.software/countries.json
- https://data.lef.software/languages.json
- https://data.lef.software/currencies.json
- https://data.lef.software/timezones.iana.json
- https://data.lef.software/timezones.windows.json
- https://data.lef.software/timezones.map.json
- https://data.lef.software/filetypes.json
- https://data.lef.software/brazil/cnae.json
- https://data.lef.software/brazil/service-codes.json
Icons are served from the /icons/ prefix. Using the dedicated icon host:
- Country icons (ISO 3166 alpha-2, lowercase):
https://icons.lef.software/countries/<cc_lc>.svg - Language icons (BCP 47 tag):
https://icons.lef.software/languages/<bcp47>.svg - Generic icons:
https://icons.lef.software/generics/<name>.svg - Filetype icons (by extension):
https://icons.lef.software/filetypes/<ext>.svg
Entry points
Section titled “Entry points”- Assets: https://assets.lef.software/
- Source repo: https://github.com/LEF-CORAGEM/assets-lef-software
Where it runs
Section titled “Where it runs”- This is typically published as a web endpoint (HTTP/S). If hosted in EVEO, it will be routed via
web.core.lef(np-web) and an NGINX vhost. - Confirm the upstream and hosting location using the Services overview.
Operational notes
Section titled “Operational notes”- Keep assets versioned and backwards-compatible where possible (avoid breaking hotlinks).
- If caching/CDN headers are in use, validate cache behavior after updates.
Repository
Section titled “Repository”Full source, master datasets, and build scripts live in the assets-lef-software repository. All published artifacts are generated from master/*.master.json using scripts/build.sh.
Known risks / failure modes
Section titled “Known risks / failure modes”- Breaking changes to filenames/paths cause 404s in downstream apps.
- Misconfigured headers lead to stale assets or security issues (e.g., wrong content type).