![](https://discuss.tchncs.de/pictrs/image/ac921854-a12e-44cf-9b8b-0eb21265e2b2.png)
![](https://lemmy.ml/pictrs/image/d3d059e3-fa3d-45af-ac93-ac894beba378.png)
Not since I’ve started working from home.
Not since I’ve started working from home.
deleted by creator
eueaouaoeuaoeuaoe
The syntax is a bit confusing. You need to leave the first “spoiler” untouched. You can delete the second “spoiler” to set the title, and then replace the three underscores ___ with your text:
"
::: spoiler my-title
my-text
:::
"
Edit: Looks like most apps don’t support this and this spoiler markdown only works in the browser.
I set it up manually using this as a guide. It was a lot of work because I had to adapt it to my use case (not using a VPS), so I couldn’t just follow the guide, but I learned a lot in the process and it works well.
I’ve tried both this and https://github.com/jmorganca/ollama. I liked the latter a lot more; just can’t remember why.
GUI for ollama is a separate project: https://github.com/ollama-webui/ollama-webui
deleted by creator
An electric toothbrush.
deleted by creator
I thought we were talking exclusively about desktops. My bad.
But not all of the data shows desktops only. The ones I linked for Japan and Africa are for computer ownership in general.
Yes. It’s even extreme in some places. For example, more than half of Australian households reported in a 2022 survey that they never accessed the internet from a desktop PC that year (source; also, paywall warning). In Hungary, desktop ownership dropped from 47.5% in 2014 to 39.2% 2019. It’s safe to assume the downwards trend has continued into 2023.
Japan dropped from 81.7% in 2013 to 69% in 2022 (this is for PC ownership in general and doesn’t differentiate between desktops and laptops) and Germany dropped from 64.5% (desktops) in 2006 to 42.9% in 2022.
Even African countries, which had depressingly low computer ownership to begin with, have seen a stagnation at around 7.5% (yes, it’s that low) between 2015 and 2019.
These are just a few examples, but you’ll see a similar trend everywhere you look. Looking at these statistics reminds me of this Apple ad: https://www.youtube.com/watch?v=zfR_Jj4grZE
Edit: WTH, Spain?
Well yes, any E-Ink device should be able to open a PDF, but PadMu gives you the ability to sync two devices so you can place them next to each other and display two pages at once. I think it has additional features specifically for working with sheet music, like an infra-red sensor for turning pages by waving your hands in front of the device. I know the Gvido has that (Edit: But the PadMu actually doesn’t; it’s all software enhancements and the dual display mode).
This review showcases the side-by-side display (double mode) feature at around 4:20. Can Onyx devices do that? I haven’t checked, but my guess is no.
I know about the Boox devices, but the double screen is the main selling point for me. As far as I know, there’s nothing similar offered by any other manufacturer out there. The PadMu comes close, but it’s two separate devices (no hinge) that you have to pair via Bluetooth and place side by side, and the pairing process is slow and cumbersome.
Something like the Gvido E-Ink tablet for working with sheet music, but without all the proprietary bullshit and closed software.
SWAG is great for overwhelmed Nginx beginners. It comes preconfigured with reasonable defaults and also provides configs for a bunch of popular services: https://github.com/linuxserver/reverse-proxy-confs. Both Bitwarden and Vaultwarden are on there.
Note that this setup assumes that you will run your service (Bitwarden/Vaultwarden) in a Docker container. You can make SWAG work with something that’s running directly on the host, but I’d recommend not starting with that until you’ve fooled around with this container setup a bit and gained a better understanding of how Nginx and reverse proxies in general work.
deleted by creator
Disco Elysium was full of such moments for me. Here’s one:
You spend a lot of time in the game basically talking to yourself and your inner voices, and one of these voices is volition. If you put enough points into it, it’ll chime in when you’re having an identity crisis or struggling to keep yourself together and it’ll try to cheer you up and keep you going. At the end of Day 1 in the game you, an amnesiac cop, stand on a balcony in an impoverished district reflecting on the day’s events and trying to make sense of the reality you’ve woken up into with barely any of your memories intact. If you pass a volition check, it’ll say the following line:
“No. This is somewhere to be. This is all you have, but it’s still something. Streets and sodium lights. The sky, the world. You’re still alive.”
This line in combination with the somewhat retro Euro setting, the faint lighting, and the sombre-yet-somewhat-upbeat music was very powerful. The image it painted was quite relatable for me. I just sat there for a minute staring at the scene and soaking it all in. Even though this is a predominantly text-based game with barely any cinematics/animations, I felt a level of immersion I had rarely, if ever, experienced before.
Oh, look at that. Someone actually made a volition compilation. 😀 This video will give you a better idea of what I’m describing: https://www.youtube.com/watch?v=ENSAbyGlij0 Minor spoilers alert!
Lmao even
“I don’t intend to live beyond 60 anyway.”
In response to your update: Try specifying the user that’s supposed to own the mapped directories in the docker compose file. Then make sure the UID and GID you use match an existing user on the new system you are testing the backup on.
First you need to get the id of the user you want to run the container as. For a user called foo
, run id foo
. Note down the UID and GID.
Then in your compose file, modify the db_recipes service definition and set the UID and GID of the user that should own the mapped volumes:
db_recipes:
restart: always
image: postgres:15-alpine
user: "1000:1000" #Replace this with the corresponding UID and GID of your user
volumes:
- ./postgresql:/var/lib/postgresql/data
env_file:
- ./.env
Recreate the container using docker compose up -d
(don’t just restart it; you need to load the new config from the docker compose file). Then inspect the postgresql
directory using ls -l
to check whether it’s actually owned by user with UID 1000 and group with GID 1000. This should solve the issue you are having with that backup program you’re using. It’s probably unable to copy that particular directory because it’s owned by root:root and you’re not running it as root (don’t do that; it would circumvent the real problem rather than help you address it).
Now, when it comes to copying this to another machine, as already mentioned you could use something that preserves permissions like rsync, but for learning purposes I’d intentionally do it manually as you did before to potentially mess things up. On the new machine, repeat this process. First find the UID and GID of the current non-root user (or whatever user you want to run your containers as). Then make sure that UID and GID are set in the compose files. Then inspect the directories to make sure they have the correct ownership. If the compose file isn’t honoring the user flag or if the ownership doesn’t match the UID and GID you set for whatever reason, you can also use chown -R UID:GID ./postgresql
to change ownership (replace UID:GID with the actual IDs), but that might get overwritten if you don’t properly specify it in the compose file as well, so only do it for testing purposes.
Edit: I also highly recommend using CLIs (terminal) instead of the GUI for this sort of thing. In my experience, the GUIs aren’t always designed to give you all the information you need and can actually make things more difficult for you.
If not friend, why friend-shaped? :(