Yep! Guess it’s time to fork!
Yep! Guess it’s time to fork!


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.


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
Really im just waiting for ladybird. I use safari on my apple devices because of battery life and Zen on Linux and Mac devices for ublock and foss. I’m ngl every time I use a chrome based browser though I’m reminded how websites are supposed to work everything is about 1 billion times faster. I sure hope ladybird will allow me to finally not browser hop / hate my browser. There’s no need for new browsers that aren’t foss at this point.