The issue is not cloud vs self-hosted. The question is “who has technical control over all the servers involved”. If you would home-host a server and have a backup of that a network of your friend, if your username / password pops up on a infostealer-website, you will be equaly in problem!
get a platinum rated power supply, if you can afford it go for a titanium. The efficiency in the power supply is half of the efficiency of the rig
reduce the number of the modules to the minimum
get a platinum rated power supply ;)
get big passive coolers, you want to idle the fans
reduce the number of usb and connectors to the minimum. Their converters are not the most efficient. Try not to connect enything on them.
NO mechanical parts (including fans or water coolers)
set schedulers to conservative or power efficient. You don’t want to spike the power just because a task is 2ms longer than expected.
pick a power efficient CPU/gpu (I think we can discard this one based in your choices)
use the latest amd adaptative undervoltage technology to ensure to reduce the wattage of the cores
try to reduce to the bareminimum the number of background tasks /services running.
And that’s all. Sometimes there is a component of trial and error because sometimes the curve performance / power is not entirely linear and you don’t want to hit exponential-non-linear zone.
Good luck and if you can post you build with numbers and some lessons learnt would be great
Just to add my experience about PSU efficiency: for low power consumption (20-50W) you need PSU rated for minimum power your system needs. So if you are idling at 30W on 700W PSU your efficiency will be super bad because that PSU was made for higher loads and you are using <10%. No matter what PSU class you choose, efficiency will be better if your usage is at 40-70% of PSU max power. This is based on testing multiple desktop ATX PSUs for my small homelab
Is there a way to self-host nextcloud by downloading one file, docker container, .nzb, .jpg, ANYTHING that includes all these parts and can just plug in and run? Is that a thing, or do all self-hosters spend every waking hour sudo updating?
Nextcloud AIO or all in one. It works relatively well. I run both my own container and an AIO instance and I’ve been pretty happy with it, I’ll likely migrate to it for my docker only one in the near future. Nextcloud AIO
I didn’t think Nextcloud AIO would actually work with existing files on a separate drive. I know it says it will … but … I’m not interested in buying a gigantic new harddrive to clone all my data to just to run one program.
Also, if it’s running in WSL or a VirtualBox VM it would be fucking hell to get it to play nice with the network.
I’ve hosted mine for years on my own bare metal Debian/Apache install and 28 is the first update that has been a major pain. I’ve had the occasional need to install a new package to enable a new feature, or needed to add new/missing indices to the database, but the web interface literally tells you how to do those things, so they’re not hard.
28 though broke several of the “featured” apps that I use regularly, like “Retention”. It also introduced some questionable UI changes that they had to fix with the recent .1 update. I’ll get occasional errors when trying to move or delete files in the web interface and everything. 28 really feels like beta software, even though we’re a point release in and I got it from the “stable” update channel.
I’m on my laptop so I thought I would elaborate on my first comment to give you things to watch out for if/when you update. I’ve been hosting mine with the zip file manually installed with my own Apache/PHP/MySQL/MariaDB setup for ages now without issue. It’s been rock solid except for, like I said, the occasional changes required to take advantage of new features such as adding new indices to the database or installing an additional php addon. Here’s the things that I noticed with updating to 28.
The 3 dot/ellipses menu was missing in the web interface and was replaced with dedicated buttons for “Download”, “Add to Favorites” and “Delete”. Shift clicking was also broken. This meant that when I, for example, take a lot of photos for a holiday, I can’t use the web interface to select a large range of multiple files and then move them all from “InstantUpload” into a more permanent album. I either had to use the mobile app, or do them one at a time. The ellipses menu, along with the options to bulk “move/copy” have been added back since then with the *.1 update, but shift clicking in the web interface to select a range of files is still broken.
The “Retention” app, which is listed as a “Featured” app doesn’t function any more. I used it to automatically delete backups of my Signal messenger, files in the “InstantUpload” folder that were over a year old, etc. You can enable it, but it doesn’t actually work and just throws errors in the log file, which is now reported in the “Overview” portion of the “Administration” page with a note of “X number of errors since somedate”, and prevents you getting the green checkmark. It’s probably safe to assume that other apps will also have issues because I had half a dozen get automatically disabled with the update.
Occasionally when I use the web interface to move or copy a file, I’ll get an error message that the operation failed. Sometimes this is true, sometimes it’s not and the operation actually succeeded. If it ends up being true and the move did actually fail, doing it again results in a successful move.
It seems like they’ve made some substantial under-the-hood changes to the user interface that shouldn’t have been shipped to the “stable” channel. It’s not completely broken, it “is” usable, especially after they restored my bulk move/copy button, but I still can’t use the Retention app, at least last time I looked, so I’ve literally got daily cron scripts to check those folders for old files and delete them, then trigger an occ files:scan of the affected directories to keep the Nextcloud database in sync with the changes. This however, bypasses the built-in trash bin so I can’t recover the files in the event of an issue. I actually considered rolling back to 27 for a bit, but decided against it, so if I were you, I would stick with 27 for a while and keep an ear to the ground regarding any issues people are having that are or aren’t getting fixed in 28.
I had been running Nextcloud on an old laptop using Ubuntu, but that machine died. I have a Windows PC originally built for gaming that I am considering using for Nextcloud. Anyone have any experience with NC and Windows? Thought on the DB switch on Windows?
100% agree with tofubi, Docker on Windows is a form of self-abuse, like cutting yourself. It’s a train wreck for anything other than a little bit of testing for development work. You will come away with a bad taste in your mouth about Docker, I avoided containers for years because I started with them on Windows docker.
I’ve run a lot of different scenarios with docker, what I’ve come down to as the cleanest and easiest to maintain is Debian 12 with the Docker convenience script. It’s fast, hassle free, and doesn’t have a bunch of layers of weirdness like using Ubuntu Server with a docker snap that makes troubleshooting a nightmare.
for anything other than a little bit of testing for development work.
It’s really awesome for development work, though. Visual Studio has built-in Docker support, so I can run my app and its unit tests on both Windows and Linux (via Docker) at the same time on the same system during development.
I use docker in vscode for latex. It saves me the trouble of having to install texlive on my system. I have a task defined that mounts my sources in and runs the compilation in the container.
Thank you, I managed to get it working with MediaMTX and DockoVPN I still don’t know how I would manage dynamic IP changes during the days I’m away, that would break the VPN
For the dynamic ip address that you can get a free domain name from afraid or noip or maybe others and point your vpn to your domain name instead of direct ip address. Following that you can run cron job scripts to ensure the ip address that the domain points to is up to date
Some systems (debian) may require this sudo usermod -a -G video www-data to make sure it will work. Because ffmpeg will be launched with the www-data user that doesn’t have access to the video cameras.
It will even turn off the camera if nobody is connected;
Use ffmpeg -f v4l2 -list_formats all -i /dev/video0 to find what formats your camera supports;
Watch the stream from VLC with the url: rtmp://device-ip/live/stream
I knew this day would come! blows the dust off my gateway machine with a P4 @ 1.6GHz Look, it’s even got a fdd, perfect for backup duty! If I could only find that Zip drive though…
I’ve been doing Linux server administration for 20 years now. You’ll always have to duckduckgo things. You’ll never keep it all in your head, even just a single server with a handful of services. Docker and containers really isn’t too hard. Just start small and build from there. If you can learn how the chroot command works, you’ve pretty much learned docker. It’s just chroot with more features.
Yep same here. Professional IT for over 25 years. Nobody knows everything. It’s ok to fail. Just keep swimming. And when you do get something working…. that high is unbelievable. It’s like a drug addiction and will drive you to do more and more. Good luck!!!
If you’re on Firefox on desktop/laptop, check out Bypass Paywall [0]. It was removed from the firefox add-on store due to a DMCA claim [1], but can be manually installed (and auto updates) from gitlab. The dev even provides instructions on how to add custom filters to uBlock Origin [2], so you don’t have to add another extension but still get some benefit.
But this is by design, snap containers aren’t allowed to read data outside of their confinements. Same goes for flatpak and OCI-containers.
I don’t use snap myself, but it does have its uses. Bashing it just because it’s popular to hate on snap won’t yield a healthy discussion on how it could be improved.
Snap sucks, but not for the reason OP stated. There's a decillion reasons for why Snaps suck, why make up a reason that applies to other formats that are actually good?
Ok then don’t publish an application that clearly needs access to files outside of the /home directory. Or at least be upfront about how limited it is when run as a snap.
I have a 20TB RAID array that I use for a number of services mounted at /data. I would like Nextcloud to have access to more than the 128GB available to /home. I’m not willing to move my data mount into /home and reconfigure the ~5 other services that use it just to work around some stupid Snap limitation. Who knows whether Snap even can access data across filesystems if they’re mounted in home. I wouldn’t put it past the Snap devs to fall down on that point either.
Yes, Docker clearly needs access to all files. It is meant for running server software, and server software is supposed to be flexible in its setup. To me, this limitation makes it completely unusable. Nextcloud is only the first service that needed access to that directory. I’ll also be running MinIO there for blob storage for a Mastodon server. I’ll probably move Jellyfin into a Docker container, and it’ll need access too.
The fact that this giant issue with Snap is not made clear is my biggest problem with it. I had to figure it out myself over the course of two hours when there are zero warnings or error messages explaining it. What an absolutely unnecessary waste of time, when it could have warned me at install that if I wanted a completely functional version of Docker, I should use the apt package.
I will never use any Snap package again. This was such a bad experience that I probably won’t even be using Ubuntu Server going forward. I already use Fedora for desktop. And the fact that a few people here are basically saying it’s my fault for not already knowing the limitations imposed on Snap packages is just making it more obvious that Ubuntu has become a toxic distro. It’s sad, because Ubuntu got me into Linux back with Hardy Heron 8.04. I’ve been running Ubuntu servers since 9.10. I used to be excited every six months for the new Ubuntu release. It’s sad to see something you loved become awful.
The issue here is that Canonical pushed the snap install without warning about its reduced functionality. I don’t think highlighting a wildly different experience between a snap install and the Docker experience people are used to from the standard package install is “bashing it just because it’s popular to hate on snap.” For example, if you take a fresh Ubuntu server 22 install and use the snap package, not realizing that snaps have serious limitations which are not explicitly called out when the snap is offered in the installation process, you’re going to be confused unless you already have that knowledge. It also very helpfully masks everything so debugging is incredibly difficult if you are not already aware of the snap limitations.
Yes, it’s been on my roadmap for a while. I also created a pull request several months ago to enter the repo but it was never accepted (it’s also my fault because I didn’t follow the verification process properly).
selfhosted
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.