We should use different credentials for every team in GerTranslateWebServer in the future.
This could easily be done by using NGINX HTTP auth. Every path beginning with /[lan]/ would be protected by its own password file. Thus we should write a script to create
a password file user_[lan] for each team (language) and
an NGINX site that restricts access to /[lan]/ to the authentication with user_[lan].
GerTranslateWebServer is already designed with this in mind and therefore uses an appropriate scheme, but some changes may be necessary. It should be ensured that all teamleaders can still see the other teams' translations, so working together is not hindered between teams nor between the teamleaders of one team.
We should use different credentials for every team in
GerTranslateWebServerin the future.This could easily be done by using NGINX HTTP auth. Every path beginning with
/[lan]/would be protected by its own password file. Thus we should write a script to createuser_[lan]for each team (language) and/[lan]/to the authentication withuser_[lan].GerTranslateWebServeris already designed with this in mind and therefore uses an appropriate scheme, but some changes may be necessary. It should be ensured that all teamleaders can still see the other teams' translations, so working together is not hindered between teams nor between the teamleaders of one team.