Adds a Front Ends link to the served schema's Settings (Network › HTTP, after General), pointing at the console's own page CustomComponent/FrontEnds. That page edits inbuxa:FrontEnds, which until now only inbuxa join or the server's environment set. The console page is inbuxa/inbuxa-admin#259.
Schema only: schema.json.gz + its checksum, written the same way tools/fork/expr-schema.py writes them (re-encoding the unchanged schema gave identical bytes first).
No permission change: reading takes sysHttpGet, saving sysHttpUpdate plus sysOAuthClientUpdate, as before.
A console without the page hides the link.
Checked locally: expr-schema.py --check, privacy-check.py, name-check.py, notice-check.py, context-check.py, the tools/fork and tools/release unit tests, version.py --changelog. The console was run against a 27.1-rc.38 server serving this schema: the link shows under Settings › Network › Web.
Adds a **Front Ends** link to the served schema's Settings (Network › HTTP, after General), pointing at the console's own page `CustomComponent/FrontEnds`. That page edits `inbuxa:FrontEnds`, which until now only `inbuxa join` or the server's environment set. The console page is inbuxa/inbuxa-admin#259.
- Schema only: `schema.json.gz` + its checksum, written the same way `tools/fork/expr-schema.py` writes them (re-encoding the unchanged schema gave identical bytes first).
- No permission change: reading takes `sysHttpGet`, saving `sysHttpUpdate` plus `sysOAuthClientUpdate`, as before.
- A console without the page hides the link.
Checked locally: `expr-schema.py --check`, `privacy-check.py`, `name-check.py`, `notice-check.py`, `context-check.py`, the `tools/fork` and `tools/release` unit tests, `version.py --changelog`. The console was run against a 27.1-rc.38 server serving this schema: the link shows under Settings › Network › Web.
The served schema's Settings section gets a Front Ends link in Network ›
HTTP, after General, pointing at the console's own page
(CustomComponent/FrontEnds). The page edits inbuxa:FrontEnds: where
inbuxa Admin and the webmail are served, the webmail's client secret and
further origins, the same thing `inbuxa join` sets from the installer.
No permission change: reading it takes sysHttpGet, as before, and saving
sysHttpUpdate plus sysOAuthClientUpdate. A console without the page
hides the link.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds a Front Ends link to the served schema's Settings (Network › HTTP, after General), pointing at the console's own page
CustomComponent/FrontEnds. That page editsinbuxa:FrontEnds, which until now onlyinbuxa joinor the server's environment set. The console page is inbuxa/inbuxa-admin#259.schema.json.gz+ its checksum, written the same waytools/fork/expr-schema.pywrites them (re-encoding the unchanged schema gave identical bytes first).sysHttpGet, savingsysHttpUpdateplussysOAuthClientUpdate, as before.Checked locally:
expr-schema.py --check,privacy-check.py,name-check.py,notice-check.py,context-check.py, thetools/forkandtools/releaseunit tests,version.py --changelog. The console was run against a 27.1-rc.38 server serving this schema: the link shows under Settings › Network › Web.