Hello, i was using taiga for my company as local and it works, but after 1 month someone trying to sign up account on local server it stuck on sign up screen, any clue?

Hello,
I need to upgrade taiga to latest version 3.3.3 from 1.8 on the production server.

-->> Do I need to follow the default upgrade process or any other steps.

-->> While executing the git pull for both the front/backend application,will the internal config changes
that was done like maild id domain port number etc change along with it or will it remain
unaffected.

Any suggestions will be highly appreciated.

Regards
jacob

Hi folks,

First of all: it's wonderful that you have support for Gogs!
However, nowadays there's a better maintained fork of Gogs called Gitea.
It has nearly 3'000 patches on top of GoGS, more maintainers, more functionality and fixes for bugs that are still present in GoGS (that's the reason why we switched once).

So there are some obvious reasons why someone rather might use Gitea instead of Gogs.
Taiga users might get the impression that Gitea isn't supported though (many won't even know that Gitea is a fork of Gogs). So I guess it would be good to make it clear in the Taiga documentation (and probably in the locales of Taiga).

In case you want to make sure that integration works, you can simply test the API integration on the official test instance at https://try.gitea.io/. There you can also find the Swagger API definition.
If you rather want to use a local Gitea instance, you might want to use the official Docker image (there's also an example docker-compose.yml).

PS: Can you point me to the open Taiga issues for these points please?

• Add comments to the connected issues on Taiga when they are created on [Gitea /] Gogs.
• Create issues on Taiga when they are created on [Gitea /] Gogs.

PPS: thank you for your work 🙏

Hi,

I needed to setup Taiga application for non-profit grassroot organization. We use a dockerized infrastructure on each server, so I looked at existing containers and all of them were outdated or incomplete, so I forked one of them and put some work in it.

I work as a devops for both non-profit organizations and in commercial work, so I wanted to contribute a little bit.

The image is flexible and easy to maintain in case of Taiga applications will be updated.
Not everything is supported (eg. custom plugins are not tested), events were not tested - the support was just kept as it was but not launched yet.

The project is WIP, I will add the documentation and the support for the events at least.
Later I will be maintaining version updates (I will have to update my installations using this image anyway).

https://github.com/riotkit-org/docker-taiga

I think you can add somewhere an information, that such project can be used.

From looking through the documentation, it looks like the installation instructions (https://taigaio.github.io/taiga-doc/dist/setup-production.html) assume that I want to install taiga under https://example.com/.

Is it possible to run taiga under a base URL of https://example.com/my/taiga/url? If so, please add information on how to do this. If it is not possible, please explicitly say so on the above mentioned doc.

Thanks!

I just wanted to know whether there is any password policy option in taiga.
This was required as part of an upcoming audit.

Hi
There are some very slight errors on the frequently-asked-questions/who-is-taiga-for page.

We re obsessed with usability

should be;

We're obsessed with usability

Next.

to manage our own projects. But

The word "but" should not be at the start of a sentence.

project management tool, or

The word "or" should not be proceeded by a comma.

May I correct these tiny errors and issue a pull request?

Please, add support for multiples languages in Taiga Support Pages.

So, we can help in translate the interface, backend and support pages to our language (in my case, to pt-BR too).

Hi guys,

I'm installing taiga on my own server by following the how to on: http://taigaio.github.io/taiga-doc/dist/setup-production.html

I followed all the steps and at this the moment I can access taiga server on my network from another computer, I can register a new user and receive mail to confirm the registration.

The problem is when I try to import my dump file that I did export from taiga.io, I receive the following message:
"Our Oompa Loompas are importing your project

This process could take a few minutes
We will send you an email when ready"

I hit the accept button but the project isn't imported and I don't receive any mail.

How can I check what is the problem?

Let me show you my configuration:
TAIGA-BACK - local.py:
from .common import *

MEDIA_URL = "http://my server ip/media/"
STATIC_URL = "http://my server ip/static/"
ADMIN_MEDIA_PREFIX = "http://my server ip/static/admin/"
SITES["front"]["scheme"] = "http"
SITES["front"]["domain"] = "my server ip"

SECRET_KEY = "my secret key"

DEBUG = False
TEMPLATE_DEBUG = False
PUBLIC_REGISTER_ENABLED = True

DEFAULT_FROM_EMAIL = "[email protected]"
SERVER_EMAIL = DEFAULT_FROM_EMAIL

Uncomment and populate with proper connection parameters

for enable email sending. EMAIL_HOST_USER should end by @domain.tld

EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend"
EMAIL_USE_TLS = False
EMAIL_HOST = "my smtp server"

EMAIL_HOST_USER = ""

EMAIL_HOST_PASSWORD = ""

EMAIL_PORT = 25

Uncomment and populate with proper connection parameters

for enable github login/singin.

GITHUB_API_CLIENT_ID = "yourgithubclientid"

GITHUB_API_CLIENT_SECRET = "yourgithubclientsecret"

from .celery import *

BROKER_URL = 'amqp://guest:guest@localhost:5672//'
CELERY_RESULT_BACKEND = 'redis://localhost:6379/0'
CELERY_ENABLED = True

EVENTS_PUSH_BACKEND = "taiga.events.backends.rabbitmq.EventsPushBackend"
EVENTS_PUSH_BACKEND_OPTIONS = {"url": "amqp://taiga:PASSWORD@localhost:5672/taiga"}

TAIGA-FRONT - conf.json:

{
"api": "http://my server ip:8001/api/v1/",
"eventsUrl": "ws://my server ip/events",
"debug": "true",
"publicRegisterEnabled": true,
"feedbackEnabled": true,
"privacyPolicyUrl": null,
"termsOfServiceUrl": null,
"maxUploadFileSize": null,
"contribPlugins": []
}

NGINX - /etc/nginx/sites-available/taiga:
server {
listen 80 default_server;
server_name _;

large_client_header_buffers 4 32k;
client_max_body_size 100M;
charset utf-8;

access_log /home/my user/logs/nginx.access.log;
error_log /home/my user/logs/nginx.error.log;

Frontend

location / {
root /home/my user/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:8001/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:8001$request_uri;
proxy_redirect off;
}

Static files

location /static {
alias /home/my user/taiga-back/static;
}

Media files

location /media {
alias /home/my user/taiga-back/media;
}
}

I hope you can help me. I really need to have taiga ready to work on a production environment in my company.

Best Regards

There is a misspelling in Support page:
https://tree.taiga.io/support/frequently-asked-questions/can-i-use-taiga-in-my-language/#how-to-help-us-to-translate-taiga-in-your-language: