Learn to self host now.

[santiago@mastodon.uy]

@vkc if PCs computing power are ment to be rented (you would not have an actual PC at home) i assume that yeu are talking about selfhosting and owning the hardware too. Interesting times ahead.

Edit: To add this https://hachyderm.io/@pheonix/115899759634576914

[bezet234@mastodon.social]

@a @vkc @redliria
Very interesting. Thanks for sharing! I will try it at some point

[eemon@social.linux.pizza]

@vkc I've got my own gitlab server running on my old PC. I want to put more services on it like a drive and mail. However that PC is running on an 8 core CPU(one of which is broken and doesn't work). I need to upgrade it.

[elena@aseachange.com]

@yunohost awww thank you for the great compliment ​ ❤️​ - delighted to hear you are recommending my guides.

And hello @Meznor ! I've been writing a blog series about how to self-host from the POV of a total newbie (that was me a year ago).

Part 1 is tech requirements: https://blog.elenarossini.com/a-newbies-guide-to-self-hosting-with-yunohost-part-1-reasons-requirements/

Part 2 is a step-by-step installation guide for the YunoHost system: https://blog.elenarossini.com/a-newbies-guide-to-self-hosting-with-yunohost-part-2-installation-setup/

and part 3 - coming tomorrow! - will show how to install an app. I'll be showcasing #NextCloud.

Feel free to reach out if you have any questions

@beaufils @vkc

[tylerparker@mastodon.social]

@vkc been meaning to get further into:
https://coolify.io/

[cypriendlp@mastodon.social]

@Meznor @vkc
I consider myself a newb, went with unraid followed it has great channels on YouTube on how to implement many services. If you want to access your services remotely I would recommend to start with tailscale so you don't have to deal with port forwarding and security.

[daria@gts.0xdj.dev]

@vkc I thought about that, but I'd still consider hiding my public IP somehow when running my server from a PC in my home - maybe it's irrational fear of exposing the network though.

[radioclash@retro.pizza]

@daria @vkc I would recommend VPS to start. I used to run my own radio station locally and uptime and opening your local LAN to attack are the main issues.

I think having a lot of open source servers open to attack is a hackers playground and most people aren't needy enough to do the opsec stuff. I know I struggled with it so have VPSes now.

I mean you have to know SOME of it but there is a whole level above of extra firewalls and DMZs etc. I don't have my NAS with a Dyndns anymore cos hacking attempts went through the roof!

[vkc@linuxmom.net]

@daria there's some good tools for that, Pangolin comes to mind- I run one on a VPS so I can share a few things with folks for testing.

Of course, keeping it behind the firewall and just using a VPN is totally fine too.

[rinkside@mastodon.online]

@vkc My setup if it helps anyone: An RPi 5 (16GB) with a Pimoroni NVMe Duo with two, 1TB SSDs. (One SSD is reserved for my backup.) Runs Raspbian Lite. Hosts my PiHole, Jellyfin, print server with plenty of room to expand to other services. Only accessible within my home network. Total cost was ~$300.

[jesse_id@theforkiverse.com]

@vkc running ingress/service swarm nodes through a cloudflare tunnel to a proxmox VM on an isolated VLAN, the way the Lord intended

[numb_comfortably@hachyderm.io]

@vkc Did this. Can confirm, it's awesome.

[eldersea@expressional.social]

@vkc While it's occasionally frustrating, I overall love it. Use Immich and Emby and Syncthing and NextCloud every single day.

[lgsp@social.tchncs.de]

@vkc

Serious question: why do you say, so? Why now?

[gumnos@mastodon.bsd.cafe]

@vkc @daria

I lean towards basing it on how tied you are to that VPS. If your VPS provider decides to suddenly double the price, or decides that your site is Bad™ and terminates it, how quickly can you migrate to a different host (whether VPS or home)?

Some of us don't have the luxury of much ISP competition, so I'm wary of running things from home, putting that connection at the mercy of our ISP's fickle whims.

(and tbh, I'm pretty tied to my VPS providers, and should take steps to untie those)

[blauertee@berlin.social]

@vkc @daria
Hmm depending on what you wanna host, and who you wanna reach, you could do it on i2p or reticulum.

[linux@mivatter.com]

I would say.... Learn to self‑host remotely.

If you’re American, the last thing you want is for everything to be stored locally on your computer and easily taken.

Due process is clearly out the window. Your rights to privacy and personal property are gone, too. People detained by ICE lose their phones and are never given them back. Your personal computer can also be seized.

Yes, host things yourself — but do it outside U.S. jurisdiction. That means avoiding large corporations like Google, Microsoft, and Amazon. Choose infrastructure overseas, where your government cannot simply claim your data or hardware.


@vkc@linuxmom.net

[mason@partychickens.net]

@vkc It's probably worth distinguishing between services to better scope the project, especially since various projects will require varying levels of public exposure and various kinds of resources.

I'd recommend starting people off with building their own firewall so they're less at risk from their own ISPs. This will be really good practice for setting up complex services like email.

#selfhosting

[pthane@toot.wales]

@vkc
I did. When it wasn't really necessary but just seemed interesting. Nothing fancy, just Nextcloud on an old desktop machine lurking in a garden shed.

[meznor@mstdn.social]

@elena @yunohost @beaufils @vkc ❤️ 😀 y'all are the best, thank you!!