IServ (school platform)

This skill uses an HTTP client (no browser automation) to log in and call IServ endpoints.

Credentials / security

• - Do NOT hardcode credentials.
• Provide credentials via environment variables.

Single profile:

• - ISERV_BASE_URL (e.g. https://grabbe-dt.de)
• INLINECODE2
• INLINECODE3

Multiple profiles (parallel):

• - set ISERV_PROFILE=<name> or pass INLINECODE5
• provide ISERV_<PROFILE>_BASE_URL, ISERV_<PROFILE>_USER, INLINECODE8

Commands

CODEBLOCK0

Notes / next steps

• - Exercises: listing/details/submission are implemented via HTML scraping.

Submission is now form-driven (parses the actual <form> on the exercise page and posts multipart), which is more robust than guessing an internal upload API. If it still fails on a specific IServ instance, capture: - the HTML of the exercise detail page (after login) - response status + redirect URL

• - Files: list/download/upload + mkdir/rename/delete are implemented as best-effort across IServ versions.

Some instances expose slightly different endpoints; the client tries to discover Symfony FOS routes (when available) and falls back to common API paths.

Ideas to extend further:

• - richer exercise parsing (due dates, teacher, description)
• announcements/news
• messenger notifications (currently experimental)
• robust file search, move/copy, and recursive folder download

Reference: IServ routes are discoverable via the bundled FOS routes JS (commonly /iserv/js/fos_js_routes.js; some instances also use /iserv/js/assets/fos_js_routes*.js).