Shanty/Main
1
0
Fork 0
Code Issues 18 Pull Requests Actions Packages Projects Releases Wiki Activity

Add multi-user support #28

New Issue
Closed
opened 2026-03-17 16:45:12 -04:00 by connor · 0 comments
connor commented 2026-03-17 16:45:12 -04:00
Owner
Copy Link

Add basic multi-user support so multiple people in a household can share a Shanty instance with their own watchlists and preferences.

  1. User accounts — basic username/password authentication
  2. Per-user watchlists — each user has their own monitored artists/albums
  3. Shared library — the actual music library is shared, but watchlists are personal
  4. Admin user — one user is admin and can manage settings, trigger system operations, manage other users
  5. Session management — JWT or cookie-based sessions for the web UI

Acceptance Criteria

  • Users can register and log in
  • Each user has their own watchlist
  • The music library is shared across users
  • Admin can access settings and manage users
  • Non-admin users can only manage their own watchlist
  • Session management works in the web UI
  • Subsonic auth maps to Shanty users

Dependencies

  • Issue #9 (web backend)
  • Issue #10 (Elm frontend)
  • Issue #6 (watchlist — needs to become per-user)
Add basic multi-user support so multiple people in a household can share a Shanty instance with their own watchlists and preferences. 1. **User accounts** — basic username/password authentication 2. **Per-user watchlists** — each user has their own monitored artists/albums 3. **Shared library** — the actual music library is shared, but watchlists are personal 4. **Admin user** — one user is admin and can manage settings, trigger system operations, manage other users 5. **Session management** — JWT or cookie-based sessions for the web UI ### Acceptance Criteria - [ ] Users can register and log in - [ ] Each user has their own watchlist - [ ] The music library is shared across users - [ ] Admin can access settings and manage users - [ ] Non-admin users can only manage their own watchlist - [ ] Session management works in the web UI - [ ] Subsonic auth maps to Shanty users ### Dependencies - Issue #9 (web backend) - Issue #10 (Elm frontend) - Issue #6 (watchlist — needs to become per-user)
connor added the HighPriority label 2026-03-19 12:30:45 -04:00
connor started working 2026-03-19 13:16:03 -04:00
connor worked for 47 minutes 2026-03-19 14:03:25 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LowPriority
MediumPriority
HighPriority
MVP
No Label HighPriority
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
connor
No Assignees
1 Participants
Notifications
Total Time Spent: 47 minutes
connor
47 minutes
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Shanty/Main#28
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?