Following up from the recent post where we introduced a $1 "non-app" tier, we've reworked the way that storage mounts work, so that not only are they now free, but they're also completely self-service!
I'll get into the technical details below, but here's a howto:
So, why the change to the previous model (purchase mount in the store, enter details, we attach it for you)?
The store method was clunky - if you entered the wrong rclone parameters, for any reason, your pods would all stall, failing to mount the storage, and you'd need human intervention to solve it, as well as cancellation and reprocessing of your order!
Zurg works differently though - there's no up-front configuration in the store, and pods will all start even before you've configured Zurg, they just won't see anything in /storage/realdebrid-zurg/.
The other rclone mounts now work the same way - all users have access to rclone-ui (it's on your dashboard), and from rclone-ui, you configure standard rclone "remotes". We'll then mount all your remotes into /storage/rclone, and all your apps will be able to "see" the storage, without even having to restart!
So the goals here were:
- Reduce user friction when attaching cloud storage
- Reduce technical issues when mounts fail
There are two possible exceptions which we're still exploring - DebridLink and AllDebrid have WebDAV endpoints, but @arvida42 (the developer of Jackettio) has recently released "davdebrid", which may let us mount DL and AD links like Zurg does, with automated sorting of media into folders.
Weekly update gets a polish
If you're subscribed to our YouTube channel, you'll have noticed the improvement in video quality recently - one of our ElfVisors has been assisting us with editing resource, and the differences are noticeable! (Also, going full-screen, faceless has been an improvement).
Here's our latest weekly news roundup:
Exploring Elf-centives for OSS development
We've been brainstorming internally about how to contribute back to our favourite opensource apps, while at the same time incentivizing features / fixes that matter to ElfHosted users. It's still a baby idea, but one idea has been to create "Elf-centives"..
An Elf-centive would be a feature / fix request captured in an issue, in a repo we manage, which has a funding pledge attached.
Once a deliverable was hammered out, ElfHosted would "take the lead" on a funding pledge, and interested users would be invited to step up and add their own support (say, if you find that Kometa is a really useful tool, and you want to "elf-centivize" a web UI development stage, or you'd like torbox support added to a Stremio addon).
Upstream developers could claim the funding by prioritizing and delivering the feature, or 3rd-parties could "sideload" the feature via ElfHosted's own build/infra system.
I'm not sure whether this'll fly yet (I'd be interested in your feedback!), but I've setup a POC to experiment with, at https://github.com/elfhosted/containers/issues/608