expose SOCIAL_AUTH_GITEA config options for docker deployment

[Bubu]

Describe the problem

We'd like to configure gitea oauth for a docker deployment. This currently requires using settings-override.py, it would be nice if it instead can be exposed like all the other oauth settings via WEBLATE_* env vars.

Describe the solution you'd like

see above

Describe alternatives you've considered

No response

Screenshots

No response

Additional context

No response

[github-actions]

This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this.

You can learn about how to get started in our contributors documentation.

[Revortni]

@nijel hey I'd like to give this a try

[nijel]

@Revortni you're welcome!

[Revortni]

@nijel The issue mentions a settings-override.py file but i couldn't find it in the code, nor could i find SOCIAL_AUTH_GITEA used anywhere. Am i missing something here?

[nijel]

The override settings is needed right now when the environment configuration is not supported. You should add something like what is used for other services:

weblate/weblate/settings_docker.py

Lines 293 to 299 in 2b93063

	if "WEBLATE_SOCIAL_AUTH_BITBUCKET_KEY" in os.environ:
	AUTHENTICATION_BACKENDS += ("social_core.backends.bitbucket.BitbucketOAuth",)
	SOCIAL_AUTH_BITBUCKET_KEY = os.environ.get("WEBLATE_SOCIAL_AUTH_BITBUCKET_KEY", "")
	SOCIAL_AUTH_BITBUCKET_SECRET = os.environ.get(
	"WEBLATE_SOCIAL_AUTH_BITBUCKET_SECRET", ""
	)

[Revortni]

ok so i looked into the social core documentation for gitea and it seems only the below code would suffice.
SOCIAL_AUTH_GITEA_KEY = os.environ.get("WEBLATE_SOCIAL_AUTH_GITEA_KEY", "")
SOCIAL_AUTH_GITEA_SECRET = os.environ.get( "WEBLATE_SOCIAL_AUTH_GITEA_SECRET", "" )

Uncertain if the api url will be needed

[Revortni]

@nijel hey there. any comments on this?

[nijel]

You also need to add the backend to AUTHENTICATION_BACKENDS (see the above example).

[nijel]

The URL is most likely needed as well to specify the gitea server URL.

[Revortni]

You also need to add the backend to AUTHENTICATION_BACKENDS (see the above example).

As you can see below the documentation does not specify any authentication backend for Gitea.

@nijel

[Revortni]

The URL is most likely needed as well to specify the gitea server URL.

Ok will add a config for this too

[Revortni]

@nijel I've mentioned my findings about the authentication backend above

[nijel]

It's generic way of enabling backends. Just look at the BitBucket example I've posted in #8205 (comment). Also, it would be great if you could actually test that the integration works...

[github-actions]

Thank you for your report; the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.