Gramex 1.86 supports API rate limiting, an improved FilterHandler, non-root Docker usage, and more.
Every handler supports rate-limiting via the ratelimit config.
For example, this allows 50 hits per user per day:
url:
page:
pattern: /api
handler: FormHandler # or any handler
kwargs:
# ...
ratelimit:
keys: [daily, user]
limit: 50
Rate limit example
FilterHandler can return ranges of values for a column using the _c=<col>|range syntax.
FilterHandler range example
For example, ?_c=c1|range&_c=c2|range returns the min and max values of columns c1 and c2:
{
"c1|range": [
{
"c1|min": 0,
"c1|max": 97
}
],
"c2|range": [
{
"c2|min": 0,
"c2|max": 50
}
]
}
This is useful for range filters like:
<input
type="range"
min="${filter['c1|range'][0]['c1|min']}"
max="${filter['c1|range'][0]['c1|max']}"
/>
FilterHandler runs a database query for each column that you request.
For slow database connections, you can speed this up with in_memory: true. For example:
url:
flags:
pattern: /filter
handler: FilterHandler
kwargs:
url: $YAMLPATH/city-products.csv
in_memory: true
When you request ?_c=city&_c=product, FilterHandler fetches all unique combinations of city and
product into memory. Then it further creates combinations.
This only runs a single query, but uses a bit more memory.
Since Gramex 1.85, Gramex Docker builds smaller images
The images now make it easier to run Gramex apps as a non-root user.
Specifically, you can run npm install -g without sudo or doas.
(Credits: Shraddheya).
Python has moved to using pyproject.toml as the standard way to package libraries.
Gramex now uses a pyproject.toml rather than setup.py.
Also, Gramex no longer ships as a conda package. Instead, you can install it with:
pip install gramex
gramex setup --all
gramex.cache.open() can now read a single Excel cell value, e.g. gramex.cache.open('file.xlsx', range='A1').handler: <HandlerName> or as handler: gramex.handler.<HandlerName>. On Windows, the latter wasn’t working. This is fixed.Gramex 1.86 is backward compatible with previous releases unless the release notes say otherwise. Automated builds test this.
Every Gramex release is tested for security vulnerabilities using the following tools.
The Gramex code base has: