1. FAQs

1.1. How can I change the domain name?

The domain name mainly affects the frontend application, because it needs to comunicate with the backend through the domain/public-ip.

To do this you should update the url value api on frontend config file dist/conf/conf.json. Also you should update the domain related configuration on the backend settings file: settings/config.py.

And finally reload the backend service.

1.2. How can I disable registration?

You can disabled public registration for external user. If you disable it, only invited users can create accounts in the instance.

If you have your installation from source code:

  • In back, set to False in settings/config.py

  • In front, set to false in dist/conf.json

    "publicRegisterEnabled": false,

If you have docker installation:

  • Set PUBLIC_REGISTER_ENABLED to false in both back and front service.

1.3. How can I restrict registration to a concrete domain?

You can restrict the usage of the platform to a set of valid email domains, so this allows you to restrict the registration to users that have a valid company email account.

To do this you should update the USER_EMAIL_ALLOWED_DOMAINS on your settings/config.py and add the list of valid domains, for example, if you want to allow registrations only from mycompany.com and mycustomer.com, y can set it as:

USER_EMAIL_ALLOWED_DOMAINS = ["mycompany.com", "mycustomer.com"]

And finally reload the backend service.

1.4. How can I restart the backend application?

To restart any application use the systemctl command:

sudo systemctl restart taiga

And finally restart the taiga-async service:

sudo systemctl restart taiga-async

1.5. How I can keep my app up to date with the most recent Taiga version?

1.6. How I can add extra functionality to Taiga?

Taiga allows adding functionality through contrib plugins. The installation of each plugin depends on the plugin itself and must be documented in the plugin repository.

The current supported plugins are here

1.7. How I can make a backup of the data? And then restore them?

To backup data from your server you just need to store a copy of the database and attachments files. That is, You just need to make a dump of the database and a copy of taiga-back/media directory.

  1. Create dump:

    pg_dump taiga > taiga.sql
  2. Copy media to a <dest>:

    cp -r taiga-back/media <dest>

Then You can restore the backup creating a new database to load the dump and copying the media directory:

createdb taiga
psql taiga < taiga.sql
cp -r <dest> taiga-back/media

2. Common Bugs

2.1. UnicodeEncodeError

If you have some error like this:

File "/home/taiga/taiga-back/taiga/projects/services/invitations.py", line 17, in send_invitation
  File "/home/taiga/.virtualenvs/taiga/lib/python3.4/site-packages/django/core/mail/message.py", line 286, in send
    return self.get_connection(fail_silently).send_messages([self])
  File "/home/taiga/.virtualenvs/taiga/lib/python3.4/site-packages/django/core/mail/backends/console.py", line 36, in send_messages
  File "/home/taiga/.virtualenvs/taiga/lib/python3.4/site-packages/django/core/mail/backends/console.py", line 23, in write_message
    self.stream.write('%s\n' % msg_data)
UnicodeEncodeError: 'ascii' codec can't encode character '\xfc' in position 487: ordinal not in range(128)

You have to change the locale of your system to someone that support UTF8 characters. To fix it add to the taiga user .bashrc file this lines:

if you have a German Linux machine, you can fix the problem by exporting the locale to de_DE.UTF-8:

export LANG=de_DE.UTF-8
export LC_ALL=de_DE.UTF-8
export LC_TYPE=de_DE.UTF-8

If you are on a US machine, en_US.utf-8 is the encoding of choice. On some newer Linux systems, you could also try en_US.UTF-8 as the locale:

export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8
export LC_TYPE=en_US.UTF-8

Restart the shell, or the machine, and try again.