Open scharph opened 7 years ago
The problem is with Taiga's use of gravatar, where it gets its avatars.
If you're NOT running Taiga on port 80 or your installation is otherwise NOT visible to the internet, you will have this problem. The fix is to edit the conf.json file in taiga-front and add a line that says "gravatar": false
.
What I did is edit the "configure" script for the taiga-front container here and rebuild it. Alternatively, you could (after Taiga startup) issue docker commands to edit / replace the config file. Like this, yours may be different depending on your docker-compose project name:
# copy the conf.json file from the running container
docker cp taiga_taigafront_1:/usr/local/taiga/taiga-front-dist/dist/conf.json .
# edit and add the gravatar line
vi conf.json
# copy the new conf.json back into the container
docker cp conf.json taiga_taigafront_1:/usr/local/taiga/taiga-front-dist/dist/conf.json
# clean up, unless you want to keep this file
rm conf.json
I suppose a more elegant solution would be to have an environment variable for the container that would do this for you.
I think the issue is other... i added my host name but it looks up only for the subdomain like:
taigaback:
image: htdvisser/taiga-back:stable
hostname: 172.10.1.1
and in the avatar URL that i upload it shows http://172/media...
i did
docker-compose -f taiga.yml
taiga.yml:
when i logged in with admin:123123 the useravatar looks like this:
What is my problem?