Setting it only rebound main.py's own module-level WEB_POOL_SIZE -
runtime.py and maintenance.py each imported their own copy at process
start (from config import WEB_POOL_SIZE), so the actual pool-sizing
logic in ensure_web_pool()/cleanup_loop never saw the change and kept
targeting the .env value. The UI control only ever changed what the
admin page displayed back to itself, plus a couple of >0/<=0 branch
checks in main.py - never the real pool. Removed the input, button,
JS handler and the dead endpoint rather than wiring the three-module
sync it would take to make it actually work.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The wall used to hide communigate-pro-user and show
communigate-pro-admin under a generic CommuniGate Pro label instead -
a dedup for when both existed as active services. ADMIN is inactive
now (deliberately, USER is the one meant to be public-facing), so the
exclusion of USER left neither showing on the wall at all. Just list
public_services as-is.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Same restructure as the Pilots tab: one form instead of two stacked
ones, a + button at the top of each list to switch it into create
mode, and an inline on/off toggle per list row. Applies to the WEB,
RDP and Users tabs - save() now POSTs when the hidden id is empty
and PUTs otherwise, delete/prewarm/icon/health/ACL boxes show only
once something real is selected.
No backend changes - the create and edit endpoints already existed
independently, this only changes which one the frontend calls.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The admin password field is gone from both the create-user and
edit-user forms. Three flows now generate a password and mail it
instead of letting an admin type one:
- create_user(): password generated, welcome email sent
(login/password/portal link) right after the row commits
- new POST /api/admin/users/{id}/reset-password: generates a new
password, saves it, emails it - the only way a password changes now
- assign_rdp_slot(): sending a user their first grant on a pilot
(not every later tweak of an existing grant's expiry - guarded by
an is_new_grant check) sends a short "you have pilot access" email,
no credentials since the account already exists
If an email fails to send, the plaintext password comes back in the
API response as a one-time fallback so the admin isn't locked out of
handing it over by hand - the frontend only shows it then, never on
a successful send.
Added two small helpers (_build_light_email, _credentials_table) so
these three new templates share the light-theme card shell instead
of re-typing it; the existing access-approval emails keep their own
inline copies untouched.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Admin Pilots tab:
- list and create/edit form merged into one - "+ Добавить пилота" at
the top of the list clears the form into create mode, clicking a
pilot switches it into edit mode (title, Delete button and icon
box toggle accordingly) instead of keeping two separate stacked
forms
- each list row gets an inline on/off toggle (⏻/▶) to flip active
without opening the form
- categories and the login/password hint field removed from the
pilot form per earlier feedback - not applicable to pilots
Access model: assigning a pilot's RDP slot to a user is now the
single action that grants them the pilot - it creates/updates their
UserServiceAccess row (with the optional expiry typed right next to
the assign dropdown) in the same call, and unassigning revokes it.
Previously slot assignment and the ACL grant were two separate steps
an admin could forget to pair up, leaving a user "granted" with no
working slot or a slot with no visible access.
Consequently: pilots are no longer listed in the Users tab's ACL
grid at all - the Pilots tab is now the only place pilot access is
managed. set_acl() was fixed to never touch pilot grants regardless
of what's posted (it used to free a user's pilot slot whenever it
saw a pilot id missing from service_ids - which happens on every
save now that the grid never includes pilots, so saving any other
product's ACL would have silently stripped every pilot grant).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Pilots are invite-only and never appear in category-browsable
self-service catalogs, so the category checklist served no purpose
there. Dropped the login/password hint field too - not requested
for pilots.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Admin: moved pilot management out of the RDP tab into its own
"Pilots" tab - dedicated list, create/edit form and slot table with
a per-slot user-assign dropdown (always on, no more is_pilot
checkbox toggling the RDP tab's slot table between two modes). The
RDP tab goes back to exactly its pre-pilots shape.
Dashboard: a granted pilot no longer sits inside the "Ваши сервисы"
grid - it gets its own <details> section above it, open by default
whenever the user has at least one pilot (and simply absent when
they have none, rather than showing empty and collapsed).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
New Service.is_pilot flag - a pilot is a Service (type RDP) that:
- is excluded from /api/public/services-by-category and
/api/request-more-access (admin-granted only, no self-service)
- still shows as a locked card on the dashboard for users without
access (Доступно по запросу section), but with a По приглашению
badge instead of the self-request button/flow
- gets its own non-clickable teaser row on the public /login page
(logos only, informational)
RdpSlot.assigned_user_id (nullable) - pilot slots are bound to one
specific user instead of being drawn from the shared pool; regular
RDP services are unaffected (field stays NULL, same pool behaviour
as before). The /go/ allocator branches on service.is_pilot to pick
the caller's assigned slot instead of any free one. Slots release
automatically (cleanup_loop) when the owning grant is revoked or
expires, and immediately on manual ACL revoke.
UserServiceAccess.expires_at (nullable) - per-grant access window,
used by pilots so their access can be shorter than the account's own
expires_at; NULL (unchanged default) means "follow the account".
has_access() and the dashboard's granted/locked split both honour it.
Admin UI: "Это пилот" checkbox on the RDP service form, an
assign-user dropdown on a pilot's slot table (replaces the
occupied-by column), and a per-pilot expiry date field in the user
ACL grid.
Schema is applied via the existing ensure_schema_compatibility()
idempotent ALTER TABLE pattern (no alembic in this project) - no
manual migration step needed, it runs at container startup.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- app/main.py: raise products_raw[:20] cap to [:200] in /api/request-access
and /api/request-more-access - was silently truncating access requests
with more than 20 selected products
- accumulated bundles/product-page WIP (config, models, runtime, templates)
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- Credentials wrapped in svc-credentials-wrap with toggle button and chevron
- Credentials hidden by default, expand on click (CSS class toggle)
- Autofill: add autofocus selector to catch fields like Zabbix name=name
- Autofill: re-fill username after password fill if Pult/Zabbix cleared it
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ruslan