Admin Dashboard / Server Settings #1283
Replies: 1 comment 1 reply
-
|
I was originally mostly interested in the active sessions, which has been working great by the way. Being able to start a scan by triggering the tasks has also been useful. Personally I wouldn't expect anything more, the config options in the web client get added/removed in sync with things being added in the server. Based on some PRs I've seen this has already been tricky sometimes. I have a slight worry that it will bring an increased burden to try and keep in sync with the options as they get added/changed/removed in the server. (Then again I have really hard time wrapping my head around swift/objectc so maybe that perception is unfounded) Moving things to a separate controller might be nice, these things certainly make some sense for tue iOS/iPadOS versions, but probably not for tvOS. So that might make it easier to 'exclude' there. |
Beta Was this translation helpful? Give feedback.
-
|
My updated goal for the Admin Dashboard is to focus on items you might need to view or change frequently from a mobile device — such as users, devices, and logs. These are dynamic elements that are updated regularly and may require a quick change on the go. On the other hand, configurations related to libraries, networking, or transcoding are likely outside the scope of a mobile app like Swiftfin. These are usually set once during server setup and rarely need adjustments afterward. Moreover, many of these configurations require operating system changes, so you’d likely need to be on a computer to handle them effectively. Fortunately, most of the heavy lifting is a one-time setup. Adding or removing dashboard buttons as needed is straightforward, and with the current View-ViewModel architecture, updating API calls looks to be very simple. Overall, there isn’t much left to finalize on this side of the project. I’m hoping to wrap it up by the end of the year (though no guarantees). Ideally, we’ll have everything ready to include in version 1.3 alongside the much more important player manager changes.🤞 I hope that helps answer and questions/concerns you may have! |
Beta Was this translation helpful? Give feedback.
-
Last Updated | 2024-11-27
Alternative Title
Why are there so many PR's from this guy?
Summary
When I started on the Admin Dashboard, I originally set out to just do the Active Sessions, but menus and settings made for pretty quick development. So, I was able to power through a lot quickly and expand my goal a little. My new goal is to try and get as close to Web functionality as possible for settings/configuration. Since Swiftfin is an official Jellyfin app, it only makes sense to me for it to handle the bulk of Jellyfin's functionality. That's not an official position, just something I would personally like to have. So, who better to build it than the sole person asking for it!
I wanted to make this discussion a place to track what I am doing, any rationale I had for skipping anything, and track where I stand in the process. None of the items below have a timeline and are, frankly, not core Swiftfin functionality. As a result, I don't want to commit to any firm deadlines, but I will check everything off as I work on it and update this list.
The restriction I’m setting is that the settings and functions I want to include in Swiftfin should pertain to values that are updated frequently. For example, user management — adding, disabling, or updating passwords — is something that changes regularly. In contrast, settings like transcoding are typically configured once during the initial server setup and rarely updated afterward.
My primary goal is to give some transparency into what I am doing and to clear out this gross PR: #1271. My current progress can be found below.
Sections
User Policy Sections can here found on the post for this PR
Activity [Hold for SDK Update]
Logs | PR
Skipped Sections
The following section are being skipped as they should be fairly static once the server has been set up. Additionally, most of these items require additional configuration at the operating system level, which would require a browser/desktop regardless.
Completed Sections
API Keys | PR
Dashboard | PR
Devices | PR
Scheduled Tasks | PR
Non-Setting Changes
In-Progress
In-Review
Completed
Old Branches
Beta Was this translation helpful? Give feedback.
All reactions