The only thing I can think of is folder structure. Is your music organised in the "Jellyfin Way"?
adamshand
joined 1 year ago
That's exactly what CalDAV servers allow. The easiest to set up is probably Baikal, but Radicale/NextCloud are also good options.
The built-in iOS/macOS Reminders.app supports CalDAV for calendars and tasks. Everything is available offline, you can add/edit/delete events and tasks, and it will sync back to the server when you are online again.
This is what Vikunja should allow, but sadly their CalDAV implementation is broken.
I use AGH on both of my servers at home and sync them with adguardhome-sync.
They are the DHCP assigned DNS servers for everyone who lives with us and all the services I run.
Use SQLite. Easy to backup, no process taking up cpu/memory, no users to manage.
It's mostly just preference. If you are already familiar with MySQL or Postgres, use what you know. If you just want simple and lightweight, use it with SQLite (no external database).
I see. I really want to use Vikjuna. If you're mostly going to use native clients, you could swap out for a CalDAV server (NextCloud, Radicale or Baikal)?
In my opinion, they do different things.
SFTP/SCP are great ways of transferring files between computers. I prefer rsync for most things because it can resume transfers and checksum results. I'd never use FTPS because SFTP/SCP comes with SSH, and why run a separate service? SSHFS is another way to use SSH to transfer files (it mounts a remote file system to your local computer so you can use all your normal file management tools).
NextCloud (and similar) do a bunch of additional things:
- Provides clients which sync files to your local computer
- Provides a web interface for managing files
- Provides ways to share files without creating accounts
- Allows connecting external storage (eg. S3)
- Provides encryption
- And a lot more
If SFTP does everything you need, that's awesome. Use it. :-)
The thing is, these sorts of losses aren't limited to selfhosting. Selfhosting introduces some new risks and reduces some other risks.
Digital data is inherently fragile. It takes active work to preserve it.
That's one of the reasons my wife and I make an actual physical photo book each year of our favourite photos.
Debian. Always Debian.
view more: next ›
This is how NFS works. Making sure that usernames and userids match on all of your servers will fix this and is by far the simplest solution. If it didn't work, you probably just made a typo somewhere.
Other options.
Use an LDAP serer (I like LLDAP) to provide a single user database for all your servers. This has lots of advantages (can provision users and change passwords for all servers in a single place). But it is fixing your problem in the same way as above (making usernames and user ids match on all of your servers).
Use Samba/CIFS instead of NFS. Because you authenticate with a user/pass all actions happen as the user you authenticate and so local user permissions don't matter.