play-with-go / gitea Goto Github PK

Now that we have reverted to using SSH keys for auth, we need a more explicit test that the SSH setup works.

This is probably as simple as a running a script that runs ssh -T [email protected]

Tested manually for now.

That way we can revert to using a more plain and simple Docker image for cmd/gitea.

Need to explain to people what gitea actually does, particularly in the context of play-with-go.dev

Might be worth initially simply linking to the play-with-go.dev contributing docs:

https://github.com/play-with-go/play-with-go/blob/main/CONTRIBUTING.md

Ideally we should move away from replicating each repo and commit to GitHub, and instead host a public (but very locked down) gitea instance. The challenge here however is that increased attack surface, security concerns etc.

There is a significant challenge/issue associated with doing this. It breaks the dev and CI setup. If we create a public gitea instance, then that implies we will switch the VCS for play-with-go.dev/userguides to that instance, and not GitHub. That means it will no longer be possible to do dev/CI runs of guides against play-with-go.dev. This might imply that we should be using a different URL in development, but again that is not ideal because there is then some runtime-translation from, say, dev.play-with-go.dev to play-with-go.dev required. And that feels ugly.