I think 2 good concepts come to mind to help you make choices:
Least privilege - Only give things/people just enough access/authority to get the job done. A good example is sonarr doesn’t need access to your personal photos to do it’s job, so don’t give it access if to them.
Defense in layers - Nothing is perfect and you can make mistakes in configuration. Don’t rely on a single point of failure to protect you. If you want remote access use a VPN. But also take steps in your network like putting a password on the logins.
Anytype is amazing, but when they give you these super long passkeys to decrpyt? That makes having to either memorize the something like 12 short words, and keep them in the exact order they tell you, you sort of have to put them in a notebook (ironically), password manager or whatever you choose to store it.
Why no real db? Those other 2 features make sense, but if the only option you can use sacrifices the 3rd option then it seems like a win. Postgres is awesome and easy to backup, just a single command can backup the whole thing to a file making it easy to restore.
I think oCIS spoiled me with regards to the database issue xD. You bring up a good point - I’ll try reinstalling Nextcloud with Postgres, removing unneeded bloat, and use it until oCIS has a “native” backend
I am playing with SFTPGO, while not being a backup solution its a great backbend supporting sftp, WebDAV and much more that you can bind with something on client side.
Currently using synchthing, but planning to switch since that is not a backup tool.
I stand with you for the subdomain and bare metal thing. There are many great applications that I’m facing trouble implementing since I don’t have control over A domain settings within my setup. Setting mysite.xyz/something is trivial that I have full control over. Docker thing I can understand to some extent but I wish it was as simple as python venv kind of thing.
I’m sure people will come after me saying this or that is very easy but your post proves that I’m not alone. Maybe someone will come to the rescue of us novices too.
No, it’s not that. The point is not that using a sub domain is easy or not, you might not have access to using one or maybe your setup is just “ugly” using one or you just don’t want to use one.
Its standard practice in all web based software to allow base URLs. Maybe the choice of framework wasn’t the best one from this point of view.
As for docker, deploying immich on bare metal should be fairly easy, if they provided binaries to download. The complex part is to build it not deploy.
But you gave me an idea: get the binaries from the docker image… Maybe I will try.
Once you have the bins, deploying will be simple. Updating instead will be more complex due to having to download a new docker image and extract again each time.
Another such application that I wish had easy implementation for what you call base URLs is Apache Superset. Such a great application that I’m unable to use in my setup.
you may need to check your server’s DNS configuration or make sure that the hostname “lemmy-ui” is correctly defined and reachable in your network. It looks like it’s expecting the lemmy-ui to be on the .57 machine. If you are expecting it on the .62 then something is misconfigured in the script.
It just looks like it can’t find that host.
Sorry I can’t be more help. I don’t run a Lemmy instance and I’m not familiar with the ansible config you are using.
selfhosted
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.