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
its interesting because even fecesbook has a setting for this
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
not even that. when setting up their first smartphone, either them or their parents just accept to create a google account
I don’t think so. way too many people approve sensitive permissions and cookie tracking without a thought, and even more just go for a gmail account no matter what
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
But I still use reddit, too, because the community is there.
federation is important not because it can be used as some kind of buzzword, but because without it, even here we would be much fewer. there would be more very small communities, which can’t interact, and overall with strictly distinct lemmy instances the whole user number would be much lower because of things people complain about a lot even this way, that there’s not enough content
also, this focuses on crypto investments of some kind, which confused me a little
did you try using tabs, or separate dashboard pages?
what’s more, that dozen one-attribute classes could have really just been a single class for the button type… and while I’m at it… 10 KB, after minification and compression?? why the fuck does a follow button need so much code?? oh! its because its made with sloppy coding just like in this example!
why did you disable that for it? genuinely interested
guess what, you don’t need to install 2 foss apps into separate android accounts for that
it just seems like they have no clue how to use their phone. or they created dozens of android user accounts, one for each app they use, which does not make any sense but really thwarts using the clipboard
the parent can only do that on devices they own. they can’t do that on classmates devices
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