Rolfsvaag_Datateknikk/Lumi
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 22 Wiki Activity

Refresh generated core route knowledge

Browse Source
This commit is contained in:
Franz Rolfsvaag 2026-07-22 10:23:48 +02:00
parent 0b3c8adbc2
commit 42a5e42d08
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
knowledge/core/lumi-core.md
View File

@ -146,6 +146,7 @@ Version: 0.2.25
- POST /admin/updates/snapshots/settings
- POST /admin/updates/core/check
- POST /admin/updates/core/apply
- POST /admin/updates/core/deploy-branch
- POST /admin/updates/core/revert
- POST /admin/updates/bot
- POST /admin/updates/core/zip
@ -694,7 +695,7 @@ Version: 0.2.25
### POST /admin/settings
- Purpose: Saves core settings from the admin settings form.
- Inputs: body: `localhost_login_password`, `localhost_login_username`
- Inputs: body: `git_branch`, `localhost_login_password`, `localhost_login_username`
- Response format: HTTP redirect after handling the request
- Access: admin access expected
- Side effects: writes or mutates server-side state; may restart or stop runtime processes
@ -1384,6 +1385,15 @@ Version: 0.2.25
- Side effects: writes or mutates server-side state; publishes or streams live WebUI events
- Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Errors are caught and usually returned as a flash message, JSON error, or error page. Most non-API POST routes are browser form submissions and usually redirect after completion.
### POST /admin/updates/core/deploy-branch
- Purpose: Checks, applies, reverts, or reports update state for core or plugin updates.
- Inputs: body: `branch`
- Response format: Form/action response; exact format was not detected statically.
- Access: admin access expected
- Side effects: publishes or streams live WebUI events
- Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Errors are caught and usually returned as a flash message, JSON error, or error page. Most non-API POST routes are browser form submissions and usually redirect after completion.
### POST /admin/updates/core/revert
- Purpose: Checks, applies, reverts, or reports update state for core or plugin updates.