taiga installation configuration
1. Introduction
This document introduces how to deploy a complete Taiga Services (each module is part of the Taiga platform).
The Taiga platform consists of three main components, each with its own dependencies at compile time and runtime:
- taiga-back(backend/api )
- taiga-front-dist(front-end)
- taiga-events(websockets gateway)(optional)
Each component can run on a unique machine, or all components can be installed on separate machines. In this tutorial, we will install everything on one machine, installing all three Taiga components. This type of setup should be sufficient for small to medium-sized production environments.
2. Overview
This tutorial assumes you are using a clean, recently updated Ubuntu 16.04 image.
Due to the nature of the front-end, Taiga is used via domain/public-ip as the front-end application runs in your browser. The frontend must be able to communicate with the backend/API, so both frontend and backend must be accessible via the domain/public-ip.
Installation of Taiga must be done by the "regular" user, not the root user.
In this tutorial, we assume the following details:
- IP: 80.88.23.45Hostname: (example.com points to 80.88.23.45)
- Username: taiga
- System ram >=1GB (required to compile lxml)
- Working directory / home/taiga/ (user default taiga)
2.1 System architecture description
This is a brief system architecture description to help you understand how Taiga is built and works . Before proceeding further with the installation, be sure to read this description for a high-level overview.
Taiga consists of 2 core (mandatory) modules:
- taiga-back
- taiga-front
taiga-backWritten in django, python3 and provides API endpoints for the front end.
taiga-front Mainly written in angularjs and coffeescript, depends on the backend.
The python backend is exposed by gunicorn (port 9001), which is a Python WSGI HTTP server. The process manager is systemd, which runs gunicorn and taiga-back together. Technically, the backend communicates with the database (postgresql), and through the frontend, it allows users to use Taiga's features. Communication between front-end and back-end is done using API.
The backend is then publicly exposed by nginx, which acts as a reverse proxy in this case. The frontend is located in the dist folder and is exposed publicly by nginx, which acts as a static web server for this case.
3 Prerequisites
Taiga consists of three modules, each of which requires different packages and third-party packages. This section collects the packages required for successful Taiga installation and configuration. In this section, we will install all dependencies for all modules, including optional modules and services.
Basic Package
The component taiga-back uses postgresql (> = 9.4) as database:
Must be installed with several third-party libraries Python (3) and virtualenvwrapper pip upgrade to the latest version
sudo apt-get update sudo apt-get install -y build-essential binutils-doc autoconf flex bison libjpeg-dev libfreetype6-dev zlib1g-dev libzmq3-dev libgdbm-dev libncurses5-dev automake libtool curl git tmux gettext nginx rabbitmq-server redis-server postgresql-9.5 postgresql-contrib-9.5 postgresql-doc-9.5 postgresql-server-dev-9.5 python3 python3-pip python3-dev virtualenvwrapper libxml2-dev libxslt-dev libssl-dev libffi-dev
This step is required before continuing with the installation!
Create a user named taiga and grant it root permissions
Do not change to the root user. The installation must be completed with the taiga user.
sudo adduser taiga sudo adduser taiga sudo sudo su taiga cd ~
3.1 Configure dependencies
Configure postgresql with the initial user and database:
sudo -u postgres createuser taiga sudo -u postgres createdb taiga -O taiga --encoding='utf-8' --locale=en_US.utf8 --template=template0
Create a user named taiga, and a virtual host for RabbitMQ (taiga-events)
sudo rabbitmqctl add_user taiga PASSWORD_FOR_EVENTS sudo rabbitmqctl add_vhost taiga sudo rabbitmqctl set_permissions -p taiga taiga ".*" ".*" ".*"
4. Backend configuration
This section helps configure the backend (api) Taiga service and its dependencies.
Download code
cd ~ git clone https://github.com/taigaio/taiga-back.git taiga-back cd taiga-back git checkout stable
Create a new virtualenv named taiga
mkvirtualenv -p /usr/bin/python3 taiga
Install dependencies
pip install -r requirements.txt
Populate the database with initial basic data
python manage.py migrate --noinput python manage.py loaddata initial_user python manage.py loaddata initial_project_templates python manage.py compilemessages python manage.py collectstatic --noinput
This will create the administrator account. The login credentials are admin and the password is 123123.
Optional: If you wish to load some sample data into Taiga, execute the following command, which populates the database with sample projects and random data (very useful for demonstrations):
python manage.py sample_data
Copy and paste the following configuration into ~/taiga-back/settings/local.py and update it with your own details:
from .common import *
MEDIA_URL = "http://example.com/media/"STATIC_URL = "http://example.com/static/"SITES["front"]["scheme"] = "http"SITES["front"]["domain"] = "example.com"
SECRET_KEY = "theveryultratopsecretkey"
DEBUG = FalsePUBLIC_REGISTER_ENABLED = True
DEFAULT_FROM_EMAIL = "no-reply@example.com"SERVER_EMAIL = DEFAULT_FROM_EMAIL
#CELERY_ENABLED = True
EVENTS_PUSH_BACKEND = "taiga.events.backends.rabbitmq.EventsPushBackend"EVENTS_PUSH_BACKEND_OPTIONS = {"url": "amqp://taiga:PASSWORD_FOR_EVENTS@localhost:5672/taiga"}
# 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 = "localhost"#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"
Verify
(optional) To make sure everything is working properly, please Issue the following command to run the backend in development mode for testing:
workon taiga python manage.py runserver
You must then be able to see the json representing the list of endpoints on the URL: http://localhost:8000/api/v1/ .
在此阶段，后端已成功安装，但要在生产中运行python后端，必须首先配置应用程序服务器。有关详细信息，请参阅本文档后面的内容。
5.前端安装
从Github下载代码：
cd ~ git clone https://github.com/taigaio/taiga-front-dist.git taiga-front-dist cd taiga-front-dist git checkout stable
复制示例配置文件：
cp ~/taiga-front-dist/dist/conf.example.json ~/taiga-front-dist/dist/conf.json
按照以下模式编辑示例配置（替换为您自己的详细信息）：
{
"api": "http://example.com/api/v1/",
"eventsUrl": "ws://example.com/events",
"debug": "true",
"publicRegisterEnabled": true,
"feedbackEnabled": true,
"privacyPolicyUrl": null,
"termsOfServiceUrl": null,
"GDPRUrl": null,
"maxUploadFileSize": null,
"contribPlugins": []}
小心使用浏览器中的复制粘贴以避免http://重复。
有taiga-front-dist，前-dist的下载和配置是不够的。下一步是在静态文件Web服务器下公开代码（在dist目录中）。在本教程中，我们使用nginx作为静态文件Web服务器和反向代理。稍后将解释nginx的配置。
推荐学习：《linux视频教程》