antsu

não foi possível tocar ‘grass’

Toca Raul!

I maintain the opinion that NixOS exists solely to make us Arch users (btw) look not as bad in comparison.

+1
This is a problem a simple spreadsheet is perfectly adequate for.

My stuff is all in docker-compose with a stack/service structure, so listing it is as simple as running tree, and reading the individual YAML files if I need in-depth details.

What you want are two servers, one for each purpose. What you are proposing is very janky and will compromise the reliability of your services.

This here OP! ☝️

Jellyfin lets you do this easily.

Mine are all anime characters. Currently I have:

• Mizuho (Onegai Teacher)
• Misaki (To Aru Kagaku no Railgun)
• Washu (Tenchi Muyo)
• Siesta (Zero no Tsukaima)
• Derfflinger (Zero no Tsukaima)

Suggest your friend to give Eturnal a try maybe. I have it running on an Oracle free tier instance, and I use it daily to have video calls with my family using Synapse/Element (and Jitsi inside Element for group calls), and it works great. The documentation is very good too.

Edit: this is my Eturnal config, for reference:

eturnal: listen: - ip: "::" port: 3478 transport: udp enable_turn: true - ip: "::" port: 3478 transport: auto enable_turn: true - ip: "::" port: 5349 transport: tls enable_turn: true realm: turn. tls_crt_file: /etc/letsencrypt/live/turn./fullchain.pem tls_key_file: /etc/letsencrypt/live/turn./privkey.pem tls_options: - no_tlsv1 - no_tlsv1_1 - cipher_server_preference

And the compose file: services: eturnal: container_name: eturnal image: ghcr.io/processone/eturnal:latest environment: ETURNAL_RELAY_MIN_PORT: 49160 ETURNAL_RELAY_MAX_PORT: 59160 ETURNAL_RELAY_IPV4_ADDR: ETURNAL_RELAY_IPV6_ADDR: ETURNAL_SECRET: volumes: - ./eturnal.yml:/etc/eturnal.yml:ro - /etc/letsencrypt:/etc/letsencrypt:ro restart: unless-stopped read_only: true cap_drop: - ALL security_opt: - no-new-privileges:true network_mode: host

I have a bunch of ST6000NM0095 (which are similar specs) in my NAS, and despite already being well used when I got them, so far only one needed to be replaced in nearly 5 years of (my) usage.

My only advice with these is: if you notice a maddening noise coming from them when they’re idle, update them to the latest firmware and it’ll go away.

+1 for Immich. It’s the most complete and competent Google Photos replacement yet.

This. And I recently found out you can also use includes in compose v2.20+, so if your stack complexity demands it, you can have a small top-level docker-compose.yml with includes to smaller compose files, per service or any other criteria you want.

https://docs.docker.com/compose/multiple-compose-files/include/