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
Thanks for the detailed answer! :) Indeed, I read that I would be limited in storage size if choosing the internal option. That said I am not sure I will be using more than 4tb in the next months, considering also that I don't have the need for 4k videos at the moment. Would it be a "waste" to just go for an internal ssd to start, and then upgrade to a larger hdd (external) in the future?
Also, sorry just to clarify, when you say
Does downloading media to the drive still counts as a viable thing to do? And I guess the on demand use would be e.g. streaming.
Sorry, on demand is not a good way to state this, it's just how my weird mind thinks of things. By "on demand", I mean, like you are actively using it to store something or view something. If you're not intentionally doing something with it, the drive should be completely idle. That's more of a target than a requirement, though. It's a way to keep storage drives tidy and not littered with temporary cache files, or databases used to store runtime state by various services. It's just a strategy I like to take, to keep bulk storage separated from the applications and services that use it.
Even if a usb drive is intended to be permanently attached, it should still be treated as a temporary component. The reason is so that if something happens and the drive is disconnected, it limits the disruption to the system. You lose your media and documents until it's reattached, of course, but the computer keeps chugging along happily.
If you use it for writing log files, then its loss can disrupt those services (and also prevent the problem from being reported). Also it'll be constantly making noise, which can be annoying.
That's my reasoning, anyway, you might prefer it done differently.
No worries! I think I got what you meant, just wanted to make sure. I agree with you to separate storage from apps and systems, in this way if something goes wrong with the main drive (I think) I should also be able to restore the system and not lose any downloaded media or data.