There are a few ways to do it, but you don’t use caddy for SSH.

• host SSH on port 22, forgejo on a different port. Expose both ports to the internet
• host SSH on a different port, forgejo on port 22. Expose both ports to the internet
• host SSH on port 22. Forgejo on port 2222. Only 22 exposed to the internet. Change the authorized_keys user of the git user on host to automatically call the internal forgejo SSH app

Last option is how I run my Gitea instance, authorized keys is managed by gitea so you don’t really need to do anything high maintenance.

~git/.ssh/authorized_keys:

command="/usr/local/bin/gitea --config=/data/gitea/conf/app.ini serv key-9",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty,no-user-rc,restrict ssh-rsa PUBLICKEYHASH

/usr/local/bin/gitea:

ssh -p 2222 -o StrictHostKeyChecking=no git@127.0.0.14 "SSH_ORIGINAL_COMMAND=\"$SSH_ORIGINAL_COMMAND\" $0 $@"

127.0.0.14 is the local git docker access where I expose the service, but you couldn’t different ports, IPS, etc.

Damn… You too?

That has not been my experience… amdgpindriver was crashing quite often, gfx ring 0 timeout. Tons of people with that problem forums. I managed to adjust some parameters and fix it eventually.

VRR doesn’t work properly, I can get it to work, burnout is a shore every time.

I have both and nvidia and an amd GPU, and with xwayland fixed, the nvidia one can run just as well.

That said, paying 2k for a GPU to have raytracing and 24gb of RAM isn’t that attractive.

distcc so you can compile on the faster ones and distribute it

Nerfing things on a PVE game that’s supposed to be fun shows a lack of creativity.

You can buff the other things while finding better ways to increase the difficulty, instead of just boosting health and throwing more enemies, but that’s the “easy” button.

I think you meant no data cap.

On nvidia, there are still too many edge cases involving Wayland that are just crippled. Orca slicer doesn’t work for me for example, you are completely missing any of the 3d accelerated graphics in there.

On the other hand, the AMD 7x00 series have different kind of bugs, with ring0 errors leading to full resets.

I think once nvidia drivers are squared out (the proprietary ones) it will be smooth sailing.

Let’s not talk about HDMI 2.1 with an AMD graphics card either…

Gigabyte is the exception, 3 HDMI and 1 DP

I have dealt with “only works in kubernetes” because developers couldn’t be bothered to make it even work on docker without all the hidden orchestration.

So, instead of documentation, they just make the service work in that one specific environment.

Ty!

While I don’t use TPM myself (I dislike being tied to a specific hardware) the way it protects you is:

Disk is protected through encryption, so you can’t remove and inject anything/hack the password.

If boot is protected/signed/authorized only, a random person can’t load an external OS and modify the disk either.

All this together would say, even if someone acquires your computer, they can’t do anything to it without an account with access, or an exploit that works before a user logs.

In a way, the attack surface can be bigger than if you simply encrypted your disk with a key and password protect that key.

You can always compile your own Iosevka and adjust several pieces, I have done that selecting what I consider the best pieces a long time ago.

The compiled font lives in an easy to access internal webserver that I just grab from every computer I use (=

Removed unreadable // Added /* */ on their own lines with fancy design above and below comments