1
0
Fork 0
mirror of https://github.com/retspen/webvirtcloud synced 2026-11-09 03:36:48 +00:00
webvirtcloud/accounts
catborise 3c6de221ca feat(admin): the admin lists as a people directory, the user form by what it allows
The Users, Groups and Removed VMs pages were bare tables: rows of
coloured icon buttons without words, five columns of small checks for
a user's role and permissions, dates broken over three lines and a
lone "+" for a new entry. The owner chose a directory layout from three
rendered options; it follows the host pages' cards:

- Each list is a card with its count and search in the header and one
  list-group item per entry, which stacks on a phone without scrolling.
- A user shows their role as a badge (Superuser, Template editor) or
  "User", Blocked as a red badge, their groups, a granted clone
  permission and live API tokens, and the last login on one line;
  role and status are searchable. Edit is the visible action, the menu
  holds View profile, Block or Unblock and Delete; Block and Delete
  are disabled on one's own account, which the server refuses anyway.
- A group shows its member and permission counts; its name opens it.
  The page's title said "Users".
- A removed VM shows its UUID, the host it left, its owners and when
  the record was made and expires.
- Logs keep their table in a card, the server search in its header,
  the count of matching rows, Done and Failed as badges, and a message
  column wide enough to read on a phone.

The user form was one long column of horizontal fields. The owner
rejected three boxed layouts and chose one led by what the user may
do: the Active switch, Template editor and Superuser as two cards,
groups as chips, the user's own permissions as switches each saying
what it allows, then the name and password and the quota folded into
details whose summaries tell their values (-1 as "any"); they open on
a new user and on an error inside them. A refused group or permission
is said beside its field. The group form follows it: the name, what
its members may do, its members as chips. Cancel goes back to the
list instead of the browser history.
2026-10-31 18:10:05 +03:00
..
migrations fix(admin): the Users pages keep an administrator in and say what their fields mean 2026-10-25 22:38:40 +03:00
templates refactor(accounts): the sign-in pages on Bootstrap components instead of signin.css 2026-10-27 19:39:19 +03:00
templatetags lint with black python. convert f style strings to old one. some small fixes 2020-11-05 12:34:31 +03:00
tests feat(admin): the admin lists as a people directory, the user form by what it allows 2026-10-31 18:10:05 +03:00
__init__.py Fixe migrations for new deployments 2020-05-28 18:19:25 +06:00
apps.py fix(accounts): migrate no longer overrides the change-password permission 2026-10-04 20:26:53 +03:00
auth.py fix(admin): a forced password change cannot trap a user or be skipped with a token 2026-10-26 10:12:53 +03:00
checks.py fix(accounts): migrate no longer overrides the change-password permission 2026-10-04 20:26:53 +03:00
forms.py fix(accounts): an email address belongs to one user, so "Lost OTP?" reaches it 2026-10-26 11:19:42 +03:00
lockout.py feat(accounts): failed logins lock a user for the address they come from 2026-10-06 11:05:03 +03:00
middleware.py feat(admin): a password an administrator sets can be one the user must change 2026-10-25 22:38:40 +03:00
models.py fix(admin): the Users pages keep an administrator in and say what their fields mean 2026-10-25 22:38:40 +03:00
otp.py fix(accounts): a username longer than the field is refused by the login form 2026-10-23 16:06:10 +03:00
urls.py refactor(accounts): the sign-in pages on Bootstrap components instead of signin.css 2026-10-27 19:39:19 +03:00
utils.py fix(accounts): SSH keys with spaced comments, one token per create, OTP errors 2026-10-26 16:14:37 +03:00
views.py fix(instances): two owners added at once keep a VM to one owner 2026-10-31 00:21:06 +03:00