Open nemonik opened 3 years ago
:cricket: :cricket:
Hi @nemonik
To add a new application in Gitlab:
Then, set variables in docker-compose.yml and remember change PUBLIC_REGISTER_ENABLED value to "True" (by default is "False") as the documentaton in "1.5. Customisation" explains.
I hope this helps and thanks for you report! We are going to improve this part of the documentation.
I had to use the following redirect_url in Gitlab: "https://taiga.example.com/login". The "/login" path is not mentioned anywhere in the doc AFAIK. If you could mention it would be great :)
Thank you for your work on Taiga !
Describe the bug
https://github.com/kaleidos-ventures/taiga-docker/#gitlab-settings
As well as, section 1.5 under "Gitlab settings" https://docs.taiga.io/setup-production.html#setup-prod-with-docker
Explains how to configure Taiga to login via GitLab, but this feature when configured does not appear to work nor are the scopes one must configure in GitLab (https://{YOUR-GITLAB}/admin/applications
How can we reproduce the behavior
Configure as your documentation describes with a self hosted GitLab, such as https://github.com/sameersbn/docker-gitlab
Workarounds
N/A
Screenshots
N/A
Taiga environment
Self-hosted. Nothing in logs from tagia-front nor taiga-back.
Arch Linux latest Chrome browser
Additional context
N/A