Who owns the mount point under /mnt? If it's owned by root you could try changing ownership of it to your user
Self Hosted - Self-hosting your services.
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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- [email protected] is allowed!
- [email protected] is allowed!
- [email protected] is allowed!
- [email protected] is allowed if topic has to do with selfhosting.
- [email protected] is allowed!
If you see a rule-breaker please DM the mods!
I tried changing it just now to me and got this error:
[username]@[hostname]:~$ sudo chown -R [username]:[username] /mnt
chown: changing ownership of '/mnt': Read-only file system
Is there a way to make it writeable? Is that something I even want to do?
Okay I managed to solve it with two things:
- in settings.json, changed umask from 18 to 2.
- in settings.json, changed incomplete dir from true to false (it didn't seem to like ANYWHERE that i put this so I just said screw it, let's not have one, it's not that big of a deal)
20mbit/s per second is not so much, but it should work. In general you have to differentiate between three things with Lemmy:
- Users on your own instance directly utilizing the client api (medium bandwidth heavy, medium CPU)
- Users from other instances indirectly accessing communities (low bandwidth, but potentially high CPU)
- Either of the above directly loading images from your instance (potentially very bandwidth heavy)
For 1: you can limit the number of people you allow to sign up on your instance (highly recommended)
For 2: this is depends on the number of subscribers and the number or external servers but overall is relatively efficient as the remote servers take most of the load, but your server will still have a high database load if remote people comment and post a lot.
For 3: Until Lemmy implements a fully image proxy, this will likely be your main problem with only 20mbit/s upload. But you can severely limit the size of images being uploaded and convert them to smaller sized webp images automatically. But if a lot of people try to download the same image from your instance, it's going to be a problem.
I think you replied to the wrong thread
indeed, thanks!
Impressive, how did you set that up?
Good luck too btw 👍