0.28.1
elements man changelog/v0-28-1One upload limit replaces the request body and rpc limits. A config that still
has maxBody or maxRpcBytes builds, but they are ignored and the 25 MB
default applies. A route with maxBody fails the build.
Changes
server.maxUploadis the one limit on request size. It replacesserver.maxBody, a route'smaxBodyandserver.maxRpcBytes.- The load balancer no longer limits request size. The app's
maxUploadis the only limit. elements versionprints the installed version.- New in the manual: an
elements runprogram that uses the database starts services itself (elements man cli). - Fixed:
elements uninstall, or a branch switch that drops a package, left a stale@typespackage that failed every build. - Fixed: an rpc message over the limit stopped the app. The call now fails with "Request too large" and the app keeps running.
Upgrade
maxUpload
server.maxUpload in config.jsoc is the largest request the app accepts, in
bytes: every request body, whatever its type, and every rpc message. The
default is 25 MB. A route's maxUpload raises or lowers it for that route,
and the routes inside a mount inherit the mount's (elements man router).
maxBody: 0 is gone: a route that takes large files sets a large maxUpload.
config.jsoc// before server: { maxBody: { json: 4194304, multipart: 104857600 }, maxRpcBytes: 67108864 } // after server: { maxUpload: 104857600 }
index.ts// before app.route({ method: "post", path: "/api/videos", handler: receiveVideo, maxBody: { multipart: 500 * 1024 * 1024 } }); // after app.route({ method: "post", path: "/api/videos", handler: receiveVideo, maxUpload: 500 * 1024 * 1024 });