I’m currently running three hosts with a collection of around 40 containers.
one is the house host, one is the devops host, and one is the AI host.
I maintain images on the devops host and deploy them regularly. when one goes down or a container goes down, I am notified through mqtt on my phone. all hosts, services, ports, certs, etc are monitored.
no problems here. git gud I suppose?
if you can do all these things properly, then there shouldn’t be too much danger in selfhosting your apps publicly.
wekan and Jotty are very lightweight and flexible.
you know what would be really helpful? cross this with data from moderation. content removals, bans, permabans.
then, layer in mods/communities and you might find why users are leaving.
and here I thought it was because I’ve blocked close to 300 users.
I2P is a secure network protocol. to your ISP it’s just an encrypted stream.
it can work across any network connection. Bluetooth, Lora, ARRL, etc.
the way I interpreted your comment presented the possibility that the ISP would cut services based on the content being hosted, not as a wide area communications disruption.
your shits gay and you sound retarded
you’re that guy. congrats!
makes sense but wasn’t that already fixed with dockers rootless patches?
question, why would you leave docker for podman?
PostgreSQL
fuckin gross!
OP ignore anyone saying wireguard is better than openvpn, it’s not. they are two solutions used to solve for multiple problems.
openvpn is highly configurable and is more widely supported across almost all platforms but the learning curve is medium to difficult.
wireguard is easier to setup for first timers and has stronger encryption but lacks multiplatform support and has shorter track record ensuring security and viability.
some say wireguard is “faster”, but I haven’t seen any real world instances of this being true unless you get close to the theoretical full saturation of a 1g interface. unless you’re dealing with HA or high throughput apps in a commercial setting I doubt you will run into that issue.
personally I prefer openvpn because I use it across multiple platforms and have peace of mind knowing it’s a tried and tested solution with decades of public and private support.
I mount them directly from the NAS inside docker volumes.
if there are any configuration/local data files that need to be persistent, those are usually kept in ~/project/{container}. the compose file is kept at the root project directory.
home user is a daemon user created specifically for running docker containers that does not have root privileges.
pihole has got the best UX for DNS management hands down. it’s easy, not overly complicated, and perfect for entry-level selfhosting.
the fact that it actively blocks ads is a bonus.
I do not recommend using a seven year old as a server for the following reasons.
overall, not worth it mate. good luck though!
this is what I’m talking about when it comes to the selfhosted communities.
if you don’t know how to properly segment and vlan your network, you have no business exposing your shit to the internet.
yes. all of the images I use are cached and stored in my locally hosted gitlab registry.
I think I’ve got around 120-140 images. a lot of what I have is just in case of an emergency.
I’ve always imagined I could build and run technological infrastructure after a social collapse or something, so I have a lot of images that could be a good basis to start with. Most OS images, popular DB images, etc. it would probably never work, but I’d rather have the option than not.