WIP Adding a toggleable additional Gitea external mirror

[craddm]

✅ Checklist

• You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
• You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
• Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).

🚦 Depends on

⤴️ Summary

Adds an optionally deployable second Gitea instance intended for use as an external mirror that can then be accessed via the internal Gitea instance.

🌂 Related issues

Relates to milestone for release 5.1.0 an all Gitea issues e.g. #1998

🔬 Tests

Ongoing

[jemrobinson]

There's a lot of overlap between this and the SREGiteaServerComponent. Can we combine both into a single reusable component?

[craddm]

Yes, that's what I'm actually doing, I just haven't pushed yet

[jemrobinson]

Suggested change

	if props.gitea_servers == GiteaServers.BOTH:
	gitea_servers = ["external", "internal"]
	else:
	gitea_servers = ["internal"]
	gitea_servers = ["external", "internal"] if (props.gitea_servers == GiteaServers.BOTH) else ["internal"]

not sure this is clearer though

[craddm]

I'm also switching to using a boolean True/False for deploying the external mirror anyway, as we'd (presumably) always want the internal one anyway

[jemrobinson]

Sounds like I should stop commenting on your WIP PR 😆

[craddm]

Already some good points to nip some things in the bud 😆

[jemrobinson]

We probably don't want don't need the external server to plug in to our LDAP directory.

[JimMadge]

Some notes on Gitea configuration here

[jemrobinson]

One other thing to consider - you'll probably want the external mirror deployed into its own subnet so that we can set the networking rules accordingly (external one will be allowed internet access but no access from workspaces; internal one will have no internet access but access allowed from workspaces).