

I don’t fully understand what you are trying to do? Are you using an Ubuntu machine, and want to access the nas and win11 storage in your filesystem? If so, just use either samba or sshfs. Easy to setup up and mount into the Ubuntu machine.
Matrix 👉 @danny:radiantfig.fyi


I don’t fully understand what you are trying to do? Are you using an Ubuntu machine, and want to access the nas and win11 storage in your filesystem? If so, just use either samba or sshfs. Easy to setup up and mount into the Ubuntu machine.


Thank you for this! I didn’t realise this existed! I will activate it on my instance 👍
Couldn’t get past the gate keepers to read that article 😕


That was a good read!!


What filling up means is that you have 16gb of ram, and if your system tries to use it all, it will freeze, crash and require hard rebooting. I have more than double your ram and have hit oom (out of memory) which is a kernel error. Is your do some research around out of memory and how to mitigate and prevent it in Linux, you’ll find multiple solutions and how to check if it is.


Could be oom? How much ram do you have and is it filling up?


Ive been self hosting for years, have a 24/7/365 web server public facing, with 20+ services hosted, including a Lemmy instance. No formal education, qualification or any actual experience in any way. Never had a single course or anything. I work as a commercial manager on complex and large infrastructure construction and engineering projects.


Honestly dd is perfect. Like you say, shrink the partition down first, DD to the new disc, swap discs. That’s it.
Setup a matrix or xmpp server for the messaging.


Welcome to the club! I too have an fyi tld!
I set my Lemmy instance a couple of weeks ago. But hosting isn’t new to me so wasn’t a huge hurdle.


I have a python weather app on my linux desktop using 37mb. 1.6gb seems a tad excessive.


A reverse proxy is the traditional safe route. Use a web server like Apache, nginx or caddy, and setup to reverse proxy all your services through port 443, and use let’s encrypt and certbot to generate and manage TLS certificates.
I host around 15 public facing web services this way using nginx.
Just be aware, this is very public facing so server security and hardening is important. Things like strong passwords, disabled root, use ssh keys instead of passwords, setup fail2ban, setup crowdsec etc.
The more modern safer way is not to truly expose to full public and use things like tailscale or cloudflare tunnels. But this relies on 3rd party servers and I’m not a fan of that, but it does bring benefits.
I enjoyed reading that. I agree with a lot of it.