Another option is subpaths: xyz.ddns.net/portainer
Just one open port, to your reverse proxy (nginx or other).
The client updating no-ip with your dynamic IP is independent of the reverse proxy software.
Another option is subpaths: xyz.ddns.net/portainer
Just one open port, to your reverse proxy (nginx or other).
The client updating no-ip with your dynamic IP is independent of the reverse proxy software.
This sounds like a FOSS utopian future :)
There’s a few projects that have started towards this path with single-click deployable apps, you could even say HomeAssistant OS does this to some extent my managing the services for you.
I believe one of the biggest hurdle for a “self hosting appliance” is resilience to hardware failure. Noone wants to loose decades of family photos or legal documents due to a SSD going bad , or the cat spilling water on their “hosting box”. So automated reliable off-site backups and recovery procedures for both data and configs is key.
Databox from BBC / Nottingham University is also a very interesting concept worth looking in to:
A platform for managing secure access to data and enabling authorised third parties to provide the owner authenticated control and accountability.
I third Proxmix
I run most stuff as Docker images inside a VM, but also a few services as LXC containers and some non-docker stuff in other VMs
Like taiyang said, SteamOS is based on Arch which is super not newbie friendly, but the desktop modes “desktop environment” is KDE which available on pretty much any Linux distro, including beginner friendly ones like (K)Ubuntu and Fedora (although I’m not sure how beginner friendly Fedora is, regarding proprietary drivers and codecs)
Like others said it’s mostly just practice.
What helps is to align the (short) ends and hold them flat between your index finger and thumb. Use your free hand to get them in order. Once they’re in order, keep holding them still between your index finger and thumb using one hand, then use your free hand to slot on the connector
Edit: also bending them back and forth a bit will soften them up and reduce them curling in all sorts of directions. It also weakens them, so don’t overdo it (mostly only works for solid cable, the type meant for permanent installations like inside walls)
Wow that’s awesome! Props to etnoy for creating such a polished PR for this feature
I can’t wait to simply point immich at my existing photo structure :)
For RPi the two major causes of issues (in my experience) are low spec power supplies and low spec SD-cards.
Power supplies drop voltage when the loads gets too high, which is especially pronounced with high power USB devices like external harddrives.
SD-cards tend to get worn out or give write errors after enough writes. Class 10 SD cards are recommended for both speed and longevity. And ideally try to avoid write intensive stuff on the SD card
“On a DVD”… 😅 in some decades that might as well be like saving your video to 8mm film. Gotta call some specialist antique dealer on the other side of the continent to find the right tech and right adapters to play it back on modern hardware
Thirding a reverse proxy. Probably Nginx Proxy Manager (NPM) is the easiest reverse proxy to get started with, if you don’t want to deal with plain nginx config files
It’s also available as a standalone desktop application, which work perfectly even when you’re offline
Yes! I can not recommend draw.io aka diagrams.net enough! (I still don’t understand why it has two names and which name is the current “correct” one)
It works both in the browser, or as a downloadable standalone application that works 100% offline.
My favourite feature is exporting PNG or PDF with the complete diagram XML embedded as metadata, which means they can be opened and edited again by draw.io
It’s very useful not only for networking, but all sorts of diagramming needs
Thanks for sharing, I have 3 hm90s I’m about to set up ( just waiting for RAM and SSDs ), these crashes sound super frustrating.
I was planning to run them detuned anyway to reduce the strain and temperature on the Power Supply, since its a non-standard USB-C which looks hard or impossible to replace if it breaks some years from now
Also some FOSS projects and some content creators use it to spread announcement
And NASA posts a lot of astronomy pictures with #astromigration
Some of the “popular twitterers” are also on Mastodon, like @georgetakei@universeodon.com , @stephenfry@mastodonapp.uk (less activity), @neilhimself@mastodon.social
I’m doing my part!
You can follow them from your already existing Mastodon (and maybe kbin?) account.
From my account on mastodon.online I just followed https://social.overheid.nl/@beheerder as a test, and I’ve already been following https://social.network.europa.eu/@EU_Commission
For some reason my server couldn’t find users from the social.bund.de when I pasted the follow-link (like https://social.bund.de/@Zoll )
By the way Mastodon has a very nice interface to subscribe to other instances. Like now when using when following the link in OPs post and opening a web browser, then clicking on a user and clicking follow, it gives the option to sign in to subscribe OR copy a link to subscribe from another instance . Then I just paste that link in the search field in my Mastodon app (logged in to mastodon.online). Hopefully Lemmy will implement that “button to copy link to subscribe from other instance” soon
Turns out the real protest was the Fedifriends we made along the way
The point isn’t to save power, the point is that the laptop is completely off. You can even take out the battery if needed
You might want to look up SMR vs CMR, and why it matters for NASes. The gist is that cheaper drives are SMR, which work fine mostly, but can time out during certain operations, like a ZFS rebuild after a drive failure.
Sorry don’t remember the details, just the conclusion that’s it’s safer to stay away from SMR for any kind of software RAID
EDIT: also, there was the SMR scandal a few years ago where WD quietly changed their bigger volume WD Red (“NAS”) drives to SMR without mentioning it anywhere in the speccs. Obviously a lot of people were not happy to find that their “NAS” branded hard drives were made with a technology that was not suitable for NAS workload. From memory i think it was discovered when someone investigated why their ZFS rebuild kept failing on their new drive.