1% CPU usages, 50% RAM usage. That checks out.

And kind of violence, serious or not, seem to result in bans from the comments I read on Lemmy.

I’m confused. Your original comment was worded as if it stood in contradiction to cico.

Does not what you said just boil down to cico works, but knowing how much energy your body uses on a daily average (o in cico) is difficult to know and to not trust random values on the internet?

I’ve heard that you cannot absorb (for lack of a better word) more that 30g of protein/day (adjust for your body weight).

Is that remotly true?

First time I hear about Resilio. Is it selfhosted?

I have used KeePass for 10+ years and used Android and Windows when I first set it up. Now I need it to work on iOS, Android, Window and Linux and moving away from KeePass was not an option I wanted to consider.

My solution is to use KeePassXC on Windows/Linux¹, KeePassDX on Android and Strongbox on iOS. To sync the file between all units, I use Syncthing (MöbiusSync on iOS). I have a server always online running syncthing to make sure that at least on node has the latest version.

The only problem I have with this setup is that Strongbox does not auto update, I have to select open existing file and select the same kdbx file (and Strongbox will update the vault etc). Saving changes does not seem to be a problem but I usually do a manual scan in MöbiusSync to make sure updates are pushed.

[1] The reason I use KeePassXC over vanilla KeePass is because the devs from KeePassXC and Strongbox communicate to make sure their applications are compatible. A file created with one works with the other seamlessly.

I have an X1 Carbon Gen 9 (so a few years old now). I wanted to replace my HDD and they (Lenovo) had videons on how to do it.

I’d say yes. But stick to ThinkPad series. I have an IdeaPad for work and I really which I told my boss to buy a ThinkPad instead. Keyboard has broken twice in 2 years.

I tried to set it up the other day and failed as well. Looking at their docker-compose examples for reverse proxy, there are a lot of environment variables not included in their original example. After adding all those variables, the container started with a message about first registration.

I haven’t tested more than that yet.

EDIT: Added it to my reverse proxy and was able to create the first account via Element.

There is not alternative that is selfhosted to my knowledge. There is PushBullet with a free tier that allows for sending files. You could also use Discord and send messages via their API, and I assume that Matrix has something similar (but I have not looked).

You could also upload them to something else (Paperless or some web/file server) and send a link in your notification. A link can be displayed as a button with actions tag.

Added to my Glance page. :-)

it’s not like I have thousands of containers running

I feel you. I have ~20 container files (some are multiple containers in one file, e.g. db and web server) and I seldom have to do changes to them. Once properly configured, I don’t really have to do anything.

Do you want to expose port 80/443 and set up a reverse proxy or do you want to use a VPN tunnel? You could just use SSH to port 80 and 443 like so: ssh -L 80:<local-server-ip>:80 -L 443:<local-server-ip>:443 <username>@<domain>

I expose port 80/443 and use Caddy as a reverse proxy together with Authelia to protect anything that I deem needs an extra layer of security. I followed this guide: https://caddy.community/t/securing-web-apps-with-caddy-and-authelia-in-docker-compose-an-opinionated-practical-and-minimal-production-ready-login-portal-guide/20465

Once setup, it is easy to remove or add a backend to Caddy and Authelia. This way does mean that you sometimes need to log in twice, but that is a small price to pay if your backend app does not support SSO (like n8n community edition).

A very simple way to set up file access is to use SSHFS, mounting the drive via SFTP. It may not be as fast as other protocols but it is simple and requires minimal setup on your server.

https://github.com/winfsp/sshfs-win
https://github.com/libfuse/sshfs

Everything was .md files on the backend, which was nice. Should make automation simple (but time consuming since you most likley have to create it yourself). The only reason I stopped using it was because I didn’t really need it.

Have a look at Tasks.md. I’ve used it before and I liked it. You can customize the CSS as well.

probably also selfhosted.

Here is a link do selfhosting it: https://github.com/TeamHypersomnia/Hypersomnia/blob/master/README_SERVER.md#docker-setup

Have you considered replace the name with input from stdin? So instead of name=synapse you could do name=$1 and have one script to use for all containers.

Never heard about The Story Graph before, but it looked cool so I created an account to check it out. I could not find any way to create custom integrations (or make any integration at all).

One option would be to pull your data from ABS via its API and then use JavaScript to navigate The Story Graph’s website to “manually” update your progress.

Edit: If you want to work with Python, someone has created a library to work against their website as if it was an API: https://github.com/ym496/storygraph-api/tree/main
It uses an HTML parser to map the response from the website.

How do you manage your containers?

If you like compose files: https://www.composerize.com/

docker run -it --rm -v <your-data-path>:/data -e SYNAPSE_SERVER_NAME=<your-public-address-subdomain> -e SYNAPSE_REPORT_STATS=no matrixdotorg/synapse:v1.136.0 generate:

name: <your project name>
services:
    synapse:
        stdin_open: true
        tty: true
        volumes:
            - <your-data-path>:/data
        environment:
            - SYNAPSE_SERVER_NAME=<your-public-address-subdomain>
            - SYNAPSE_REPORT_STATS=no
        image: matrixdotorg/synapse:v1.136.0
        command: generate

docker run -d --restart=always --name synapse -e SYNAPSE_REPORT_STATS=no -v <your-data-path>:/data -p 8008:8008 matrixdotorg/synapse:v1.136.0:

name: <your project name>
services:
    synapse:
        restart: always
        container_name: synapse
        environment:
            - SYNAPSE_REPORT_STATS=no
        volumes:
            - <your-data-path>:/data
        ports:
            - 8008:8008
        image: matrixdotorg/synapse:v1.136.0