Perhyte

joined 1 year ago
[–] Perhyte@lemmy.world 7 points 6 days ago

Clearly he's actually the BBEG lich in disguise. Time for a phylactery hunt! ;)

[–] Perhyte@lemmy.world 6 points 1 week ago* (last edited 1 week ago) (1 children)

Have you also enabled Bot Fight Mode? (There's a setting to "Block AI bots" that seems useful in your situation)

[–] Perhyte@lemmy.world 4 points 3 weeks ago* (last edited 3 weeks ago)

In Europe I get a voting pass sent in the mail for every election. To vote I have to show both this pass and a valid ID.

In the Netherlands it doesn't even have to be a valid ID. If it hasn't been expired for more than 5 years it's fine for voting purposes.

[–] Perhyte@lemmy.world 2 points 3 weeks ago

Try exiting it and then make sure no tmux process is still running, by for example running ps -aux | grep tmux.

For future reference: the command to kill the tmux daemon (and as a side-effect, all other running tmux processes connected to it) is tmux kill-server (or in tmux, typing :kill-server, assuming default keybindings).

[–] Perhyte@lemmy.world 3 points 1 month ago* (last edited 1 month ago) (2 children)

The -b in crond -b means to run it as a daemon (in the background), though it appears that is also the default (source). This means the script will continue, but since that's the last line it exits. With the entrypoint stopped, the container also stops.

The fix should be to replace that line with exec crond -f so the crond process runs in the foreground and becomes the main process running in the container, replacing the entrypoint script. crond -f without exec should also work, but that needlessly keeps an extra process (the shell running the entrypoint script) alive.

[–] Perhyte@lemmy.world 28 points 1 month ago (1 children)

You don't actually have to set all the modification dates to now, you can pick any other timestamp you want. So to preserve the order of the files, you could just have the script sort the list of files by date, then update the modification date of the oldest file to some fixed time ago, the second-oldest to a bit later, and so on.

You could even exclude recently-edited files because the real modification dates are probably more relevant for those. For example, if you only process files older than 3 months, and update those starting from "6 months old"^1^, that just leaves remembering to run that script at least once a year or so. Just pick a date and put a recurring reminder in your calendar.

^1^: I picked 6 months there to leave some slack, in case you procrastinate your next run or it's otherwise delayed because you're out sick or on vacation or something.

[–] Perhyte@lemmy.world 6 points 1 month ago* (last edited 1 month ago)

These signs were detected higher in the atmosphere, where the temperature and pressure are more reasonable. And since it took until now to detect the presence of the ammonia, it's probably not a large component of the atmosphere.

So not boiling hot and probably not that much ammonia. That still leaves the thick clouds of sulfuric acid though, those are still very much a thing any probe or mission to Venus would have to be able to deal with.

[–] Perhyte@lemmy.world 19 points 1 month ago

If you don't mind using a gibberish .xyz domain, why not an 1.111B class? ([6-9 digits].xyz for $0.99/year)

[–] Perhyte@lemmy.world 2 points 1 month ago

Any chance you've defined the new networks as "internal"? (using docker network create --internal on the CLI or internal: true in your docker-compose.yaml).

Because the symptoms you're describing (no connectivity to stuff outside the new network, including the wider Internet) sound exactly like you did, but didn't realize what that option does...

[–] Perhyte@lemmy.world 2 points 2 months ago* (last edited 2 months ago) (1 children)

It also means that ALL traffic incoming on a specific port of that VPS can only go to exactly ONE private wireguard peer. You could avoid both of these issues by having the reverse proxy on the VPS (which is why cloudflare works the way it does), but I prefer my https endpoint to be on my own trusted hardware.

For TLS-based protocols like HTTPS you can run a reverse proxy on the VPS that only looks at the SNI (server name indication) which does not require the private key to be present on the VPS. That way you can run all your HTTPS endpoints on the same port without issue even if the backend server depends on the host name.

This StackOverflow thread shows how to set that up for a few different reverse proxies.

[–] Perhyte@lemmy.world 3 points 2 months ago (4 children)

Is this just placing them vertically, nothing else?

I currently use the Tree Style Tab extension and really like how it handles sub-tabs and allows collapsing the tree nodes. If I can't have that this is probably not directly useful to me unless extensions can add that functionality.

I guess I'll be watching how this evolves though.

view more: next ›