Take a distro with a package manager you are familiar with. Debian should do it.
And try out docker it’s really easy to learn and straight forward.
Jellyfin has a well documented docker compose.yml which is just a textfile that points out the facts like used versions, environment and volume paths.
I did a transition from my docker compose tools to a new system in under an hour yesterday. All I had to do was backup the volumes or data paths. Firing up the containers looks like a new install but it’s just downloading the container and everything runs like before without losing any config.
As someone who used caddy over years, I can’t completely agree.
Caddy has some downsides (nextcloud needs special setup for example) and not everyone is familiar with writing a Caddyfile. (Json)
For someone new I would recommend “nginx proxy manager”. Easy to install with docker and self explained through GUI.
I know about the successful help being an alternative to apple/google. When I start degoogling (5 years ago) nextcloud was impressive. But I talk about my own experience. And nextcloud doesn’t work on their basics. Instead they’re following every hype with an alpha app which doesn’t get support when the hype ends (nextcloud social) for example.
Maybe they could fork owncloud again? Owncloud worked over years to get rid of php and released last year “infinity scale” its a single binary. You can run it nearly out of the box. And it is stable and fast. Nextcloud needs this, too.
The php part is something a newbie wouldn’t easy success with. The alternatives I recommend are all easy to install docker containers, which are simple to maintain and no worries about the next release could break everything.
I am driving away from nextcloud more and more. I would be back when they get rid of php and really develop even one plugin (the so called “apps”) which isn’t just an alpha version.
I don’t see any use case for this bloated all in one monster with crap performance. Someone needs his files in a browser and overall synced. Use syncthing and something like filebrowser or filestash. Photos? Immich. Documents? Paperless. Music, Movies, e-books? Jellyfin. Collaborative Docs? Onlyoffice, cryptpad. Notes? Joplin, trillium. etc.
Paperless was my docker training program. I did so many mistakes and end up losing my database 3 times. My fourth try, runs smooth and I backup everything regularly. Actually 1.300 documents.
After indexing everything, I learned loving the archive feature. Docs I scanned, and don’t want to trash in real got a number in paperless and the same number in the paper folder.
it will ultimately look like a copy, and each successive copy from that copy will look worse. This is of course true with forms of tape media and a lot of others. But it isn’t true of digital media, where I could share a bit-for-bit copy of data that is absolutely identical to the original.
There is one exception: reposted memes, they are losing pixels more and more. /s
I was familiar with just organise my docker-compose containers without any frontend. But I discovered casaOS, which make things pretty simple. An AppStore and a SMB-Shared File manager gave me a really good workflow. Things that aren’t on the AppStore can be handled outside of Casa, too.
PS. But never make the mistake to integrate the outside handled containers, this mess things up.
Easy, I always mirror my cloud. My setting is: cloud is extern and in my network there is always the same copy of everything on a simple smb-nas.
My house burns to the ground (or easier, the NAS is broken) = online backup
The online provider got hacked = No problem, I have an backup at home.
The hackers burned my house down at the same time they killed my cloud = Well fuck.
PS. Since the most syncs are going directly to the cloud its just an rclone cronjob every night to backup everything on the NAS.
I tried to set this up beside my existing mailcow server. Mailcow runs smooth and has a web interface. And I am not on my way to ditch it just for jmap.
Idk, what’s happening earlier:
1.dovecot integrates jmap (I would stay with mailcow) 2. More clients support jmap (eventually switch to stalwart) 3. Stalwart get an webinterface (eventually switch to stalwart)
Using it for a month actually, I like the idea of database-notes. And I use the sharing function a lot, because I wrote a lot of guides which I share with friends and colleagues. It just transfer a note into a website and now it replaced my wiki.js and my notes app.
What I miss is a cool app, but hey it’s open source I don’t complain.
Changing stuff and seeing what happens!
The best part is remembering every change to revert it after XY change does it right.