I don’t have an explicit config file no, I don’t remember needing it before though. I’ve followed the steps https://docs.gitea.com/installation/install-with-docker which worked with gitea but doesn’t work with forgejo. I didn’t see anything that mentioned needing a config for the first method listed there at least. I suppose I could try some of the other methods listed there but I liked option A the best generally.

Logs for what the container?

I did check that first after a lot of googling and I think everything is all set there

Ok. The issues lies somewhere in the actual connection. Adding ssh keys to my instance shows up properly in the known keys. Whenever I attempt to connect either on the actual server itself as a test or via trying to clone over ssh or even connect via ssh itself I get public key denials. If you want I can provide you my ssh config on server, my docked compose file, the verbose output of the ssh connections in various facets although they haven’t appeared to be very helpful, or whatever else can be helpful

Edit would someone like to enlighten me why they’re randomly downvoting this? Would you all have preferred I just dumped logs? I genuinely don’t understand. My main question was actually whether there is a difference between gitea and forgejo since I’ve already verified this exact setup worked there. So if anything an answer to my original question would require 0 input from me. I do appreciate the help from everyone but to say that me saying “it doesn’t work” is unhelpful is missing the point

Huh does that actually work?

Edit: I realize it probably should given my understanding of tokenization but if it’s training data couldn’t it easily be replaced with like a regex or something?

Can someone explain why so many people use thorns everywhere?