Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I'll ask the question why do you want something hosted, if you don't want the files to be on the server too, or at least accessible via a mount. There's a couple projects who do that for a reason, you can't just upload an 80gb video file through a web interface simply. For home use it makes more sense for it to be connected to some sort of nas and you point it to the file on the nas, and then point where on the nas you want the output file.
As written, I don't think you'll find a lot. I think what may serve you better is finding a server solution that watches a directory and then runs transcodes based on pre defined templates, and spits them back out in a known location.
Because I want to be able to transcode files from my phone, or from any device without having to install anything.
The problem exists of how do you get files to the server. Again for a big video file you need a place to have the original accessible for the entire duration of the transcode, and you need a drop point to place the file when it's done. And if you're doing that, more than likely you have something like Plex or jellyfin, so why not just hook it up to your existing file locations?
I run jobs all the time from my cluster, but the issue always comes back to persistent storage. Where are the files you need to act on, and where should the finished results be placed? You're trying to skip those important steps here.
It was meant to run on a server with pretty much nothing on it but yea, if uploading big files isn't possible through a browser, I'll find other solutions. I was hoping files smaller than like 4GB would be fine.
About the storage, I hoped that it would just either load the file in memory, or store during the transcode, then when done, delete the source file and put the transcoded server for a limited amount of time (1h for example), then wipe it (or just wipe it after download)
Yea, I'd take the approach of having the server monitor a folder, and then just drop files in that folder to be converted.
There are a number of ways to transfer files to that folder, tools like FolderSync (Android), Syncthing or Resilio (every OS) can handle this.
Mhh, yea that seems like the obvious workaround, but not the ideal solution
Possible? Probably.
Practical? Nope!