Add DeckyParty File Manager

[39sdev]

Add DeckyParty File Manager to Plugin Store

This plugin allows users to manage their home directory & external storage via the small but immensely powerful copyparty file server.
A similar Plugin already on the Store would be DeckyFileServer,
the key advantages of DeckyParty being:

• no required root access
• forced password authentication, the password being different for each session.
• exposes all automatically mounted partitions in /run/media/<user>/, so that users can seemlessly manage their sd card files aswell.
• it's using copyparty

• meaning instead of just being able to navigate the filesystem, uploading and downloading single files; Copyparty enables the user to essentially do full user filesystem management (bulk)- uploading / deleting / moving / renaming / creating / editing, mounting it on another device as a Network Storage and more.

Task Checklist

Developer

• I am the original author or an authorized maintainer of this plugin.
• I have abided by the licenses of the libraries I am utilizing, including attaching license notices where appropriate.

Plugin

• I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
• I have verified my plugin is unique or provides more/alternative functionality to a plugin already on the store.

Backend

• No: I am using a custom backend other than Python.
• No: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
• No: I am using a custom binary that has all of it's dependencies statically linked.

Community

• I have tested and left feedback on two other pull requests for new or updating plugins.
• I have commented links to my testing report in this PR.

Testing

• Tested by a third party on SteamOS Stable or Beta update channel.

[github-actions]

Issues Found

No issues with your PR description were found.

Next Steps

1. If we found any issues above, please edit your pull request description to resolve them and leave a comment saying you've done so.
2. For the quickest review, please see the Community section of the pull request template for how you can help other developers.
3. Once your description is correct, a maintainer will review your pull request as soon as possible.

Thank you for your contribution! If you need any help, please reach out on our Discord server. ❤️

[EMERALD0874]

My only concern is "DeckyParty" is a fairly non-descriptive name that sounds more like a gaming plugin than a file server. Have you considered any other naming options? If you're sure this is the name you like, let me know and I'll move it to testing store.

[39sdev]

My only concern is "DeckyParty" is a fairly non-descriptive name that sounds more like a gaming plugin than a file server. Have you considered any other naming options? If you're sure this is the name you like, let me know and I'll move it to testing store.

Good Point. [UseCase]Party has been a common instance naming scheme in the Copyparty Community, that's why I didn't really give it any second thought...

Should I just go with "Copyparty", "DeckyParty FileServer" or "Copyparty for Decky"? Although that last one might be too long to properly fit.
Any suggestions?

[39sdev]

@EMERALD0874 settled on DeckyParty File Manager.
Paired with the plugin description & tags, it's nature should now be clear enough.

[9001]

I noticed that the full release of copyparty itself is commited into the git repo; this means that the git-repo will grow by at least 1 megabyte every time there is a new version. Over time, this will make it really big.

I'm not sure how easy the following would be to do, since it depends on how the rest of the tooling works (and I don't know anything about that), but:

A better approach would be for https://github.com/39sdev/Decky-CP to include an https-link to either the latest release or a specific version -- for security, it could link a specific version and expect a particular checksum, to ensure it hasn't been tampered with. Although the benefit of using a link to the latest version would be that users could/would automatically get the latest version of copyparty, which could have relevant bugfixes included. I do try my best to not make breaking changes, so I'd like to say that using the latest version should be fine.

[EMERALD0874]

I'll try to review this tomorrow, but 9001 raises a good point. @39sdev, you may want to check how Decky Framegen uses our remote binary system in its package.json here. Like 9001 suggested, it'll download whatever release you mention and check for a specific checksum when installing the plugin with Decky.

[39sdev]

Thanks for the reference! I've switched over to using the remote binary download system.

However, providing the latest version without a plugin update would be pretty cool, especially since I doubt Copyparty will do any fundamental changes to how it's arguments are structured in the future.

Would I be allowed to add a version check / update mechanism inside of the plugin? or is this strictly forbidden due to security concerns?

[github-actions]

This pull request is stale as no updates or testing reports have been posted within the last 7 days. Please ensure you are actively recruiting testers or resolving the issues discussed. If you do not remove the stale label or comment, this will be closed in 7 days. Please close this pull request if you need more time to resolve issues so we can keep our repo healthy.

[KingIzzymon]

(Please don't let this die... ❤️)

[39sdev]

Not intending to.
Can't really expect people to be code checking during the holidays though.

This should be ready to go in it's current state.

[EMERALD0874]

LGTM for testing

[39sdev]

What about the pending testing_env check?

[EMERALD0874]

Fixed, my bad