Open galal-hussein opened 8 years ago
Exactly, the template has several errors :
Hi, I taiga-docker setup is kinda tricky, at least imho - especially if you want to have full setup with events part and for example some plugins where you have to adjust back&front - we ended up with custom docker-compose script based on few available solutions. It's not really sharable in current form and I doubt it will ever be, but I would suggest just customizing it for you needs - it takes some time to dive into taiga itself, but it's totally worth it - it's an awesome piece of software <3.
I'm aware that this comment is not very useful, but I just wanted to say that templating taiga in some cases might be not even possible /shrug
I'm trying to fix this #242 pls take a look
@KartoffelToby I am still having the same problem, also when i try to access the service over HTTP i am being redirected to Location: https://_/
:+1:
@galal-hussein
Is it the exact same error? over https it should work
http isn't working at all you're right, i'm sorry i'm prefere only the https way, but i will change the configuration to switch between https and http in rancher.
Getting the same https://_ redirect issue. Using an nginx proxy, Tried proxying both https and http from taiga to nginx, nginx is serving https with the valid certificate.
Have you found the solution for the https://_ redirection issue?
Never found a reliable solution to having taiga behind a proxy. I spent a solid day trying to get it working with all sorts of nginx params and header forwarding. Had to eventually use a different docker image and forward 80 and 443 to taiga. Even then, was still having issues with certain things (like the admin panel) not working correctly or having the CSS broken.
Eventually realized, after updating Gitlab, that it has a Kanban style board available, and it serves my purpose. I have since dropped trying to get taiga working in a production type environment.
I solved the https://_ redirection issue by opening the port 443
in the taiga
service
Temporary fix for http
Create default.conf anywhere you want
server {
listen 80 default_server;
server_name _;
large_client_header_buffers 4 32k;
client_max_body_size 50M;
charset utf-8;
index index.html;
# Frontend
location / {
root /usr/src/taiga-front-dist/dist/;
try_files $uri $uri/ /index.html;
}
# Backend
location /api {
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://127.0.0.1:8000/api;
proxy_redirect off;
}
# Django admin access (/admin/)
location /admin {
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://127.0.0.1:8000$request_uri;
proxy_redirect off;
}
# Static files
location /static {
alias /usr/src/taiga-back/static;
}
# Media files
location /media {
alias /usr/src/taiga-back/media;
}
# Events
location /events {
proxy_pass http://events:8888/events;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_connect_timeout 7d;
proxy_send_timeout 7d;
proxy_read_timeout 7d;
}
}
{
"api": "http://change.this.to.your.domain.or.ip/api/v1/",
"eventsUrl": "ws://change.this.to.your.domain.or.ip/events",
"debug": false,
"debugInfo": false,
"defaultLanguage": "en",
"publicRegisterEnabled": false,
"feedbackEnabled": false,
"privacyPolicyUrl": null,
"termsOfServiceUrl": null,
"maxUploadFileSize": null,
"contribPlugins": ["/plugins/slack/slack.json"]
}
Enjoy
After opening a public port to map to 443, I get this error:
Rancher Version: build-master:v0.20.0
Docker Version: 1.11.2
Catalog Template: Taiga template
Taiga template is giving error whenever i try to sign in or sign up:
The logs of the container:
postgresql:
tiagback: