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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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
Can you please explain to me the difference? How does a swapdisk compare to RAM? I don’t mind googling it but I highly doubt I’ll get a straightforward ELI5 style answer from there.
I would really appreciate it if you can elaborate, if you have the time that is.
Thank you.
It just compresses your ram contents so you can fit more stuff in memory at once
There are two types of computer memory that fundamentally matter on the consumer level:
Solid state disk storage, and in particular some SD cards, can be vulnerable to excessive writes.
Ram, however, is not impacted by the number of uses.
A swap file works like this: When memory gets full, you move the least-used parts onto the swap file.
A normal swapfile is on-disk. When memory gets close to full, the system moves some onto the (much much slower, like 10-1000x) on-disk swapfile.
Zram swap creates a compressed swapfile out of your free memory. A file in linux does not have to be on a hard disk/ssd, it just has to look and quack like a file. When memory gets close to full, the system copies some onto the in-memory compressed file. This is very fast, but uses some cpu. It doesn't touch your drive storage.
That is a great explanation. It makes perfect sense to me know. Thank you
Basically zram is compression inside ram