a firewall can be used to filter incoming traffic by its properties. most consumer home routers don’t expose the firewall settings

OP is actually a bot. so many posts within an hour regularly, and compared to that, very few comments. whoever controls the account is not here to have a discussion

deleted by creator

oh! I don’t know how nix containers work, but I would be looking into creating a shared network between the containers, that is not the normal network.

you have completely lost your mind.

wtf is wrong with you. they claim its in the published epstein files package. the least they should do is link to it and show quotes

oh, I see what you mean!

they do that for the sake of providing an example that works instantly. but on the long term it’s not a good idea. if you intend to keep using a service, you are better off connecting it to a postgres db that’s shared across all services. once you get used to it, you’ll do that even for those services that you are just quicly trying out.

how I do this is I have a separate docker compose that runs a postgres and a mariadb. and these are attached to such a docker network, which is created once with a command, rather than in a compose file. every compose file where the databases are needed, this network is specified as an “external” network. this way containers across separate compose files can communicate.
my advice is its best to also have this network as “internal” too, which is a weird name but gist is, this network in itself won’t provide access to your LAN or the internet, while other networks may still do that if you want.

basically setup is a simple command like “docker network create something something”, and then like 3 lines in each compose file. you would also need to transfer the data from the separate postgreses to a central one, but thats a one time process.

let me know if you are interested, and I’ll help with commands and what you need. I don’t mind it either if you only get around to this months later, it’s fine! just reply or send a message

just to be clear, are you saying that most beginners just copy paste the example docker compose from the project documentation, and leave it that way?

I guess that’s understandable. we should have more starter resources that explain things like this. how would they know, not everyone goes in with curiosity to look up how certain components are supposed to be ran

almost every self hosted service needs a database. and what “another” database? are you keeping separate postgreses for each service that wants to use it? one of the most important features of postgres is that it as a single database server can hold multiple databases, with permissions and whatnot

I think it depends. when you run many things for yourself and most services are idle most of the time, you need more RAM and cpu performance is not that important. a slower CPU might make the services work slower, but RAM is a boundary to what you can run. 8 GB is indeed a comfortable amount when you don’t need to run even a desktop environment and a browser on it besides the services, but with things like Jellyfin and maybe even Immich, that hoard memory for cache, it’s not that comfortable anymore.

its probably hoarding it as “cache” when it thinks no other program needs it. maybe it would release some when the system has memory pressure, but this is terrible because those mechanisms are reacting very slowly

What if you want a cookie, but not enough to go to the grocery store and buy some cookies?

I fixed that for you:

What if you want a cookie, but not enough to go to the grocery store and buy some cookies, after showing your ID card for its number to be written up?

I’m aware of what the arr stack is for generally, but not with overseerr and jellyseerr

I’m aware of what the arr stack is for generally, but not with overseerr and jellyseerr

ok, but why do I want to use this? what does it do? what is its purpose?

the healthcheck URL should point to some HTTP API that the container makes available, so it should point to the container.

in place of localhost should be the container’s name, and port should be the port the container exposes as the web server. some services, like Jellyfin, have a specific webpage path for this purpose: https://jellyfin.org/docs/general/post-install/networking/advanced/monitoring/

and others, like gitea, hide the fact well that they have a health check endpoint, because its not mentioned in documentation: https://github.com/go-gitea/gitea/pull/18465

but check if docker’s way of doing healthchecks produces a lot of spam in the system log, in which case you could choose to just disable health checking, because it would push out useful logs

a better analogy would be people who write software for the cameras. screenwriters are closer to software testers

People who’ve written doctoral theses on machine learning and and natural language processing have asked me for help building their gaming rig.

I think that could still be different. knowing the internals of the computer is different from knowing which brand to buy, how to combine, compatibility, drivers, etc

tower is fine, but I think what you mean is the desktop PC. and the little square ones are the mini PCs

oh I thought it’s a joke that things are defined, or others are “immediate from” something else, while actually not. like how they love to teach this topic without explaining what is necessary