![\"Taiga](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/taiga-and-raspbian-icon.gif\"){kind=icon}
<\/p>\n<\/p>\n
A project management platform is useful for us to keep tabs on what we want to build. Taiga<\/a> is a popular open source project management platform that is highly recommended by opensource.com<\/a> to be the top open source alternative to Trello.<\/p>\n Taiga runs well on a Raspberry Pi 3. If you want to setup something at home to help you manage the projects that you are working on, you can consider setting up the Taiga project management platform on a Raspberry Pi 3 with Raspbian Stretch Lite as the base operating system<\/a>. <\/p>\n This post is adapted from Taiga's installation guide<\/a> to serve as a guide to setting up Taiga project management platform on Raspberry Pi 3 with Raspbian Stretch Lite.<\/p>\n As a first step setting up your Taiga project management platform on Raspberry Pi 3, follow this tutorial to setup Raspbian Stretch Lite on Raspberry Pi 3 to run Python 3 applications<\/a>. After doing so, you will get your Raspberry Pi 3 running the Raspbian Stretch Lite operating system with the following software pieces:<\/p>\n Apart from the Python packages that we had installed earlier, there are more dependency packages that we need to install for the three modules that made up the Taiga project management platform. To install those packages, run the following commands: <\/p>\n Once you had installed all the dependency packages needed by Taiga project management platform, proceed on to create a system user You will need to use the Once you had switched over to the Once you had configured PostgreSQL for the Taiga project management platform, run the following commands to configure RabbitMQ<\/a> for Once you had created the RabbitMQ user and virtual host for it, create a After the creation of the Run the following commands to download a copy of Taiga backend:<\/p>\n Run the following commands to create a virtual environment for Taiga backend:<\/p>\n Run the following commands to install Taiga backend dependencies in the virtual environment that we had created earlier:<\/p>\n Run the following commands to populate the database with some initial basic data:<\/p>\n This will create the administrator account with login username admin<\/strong> with password 123123<\/strong>.<\/p>\n Run the following command to get nano to create the initial configuration file for taiga backend:<\/p>\n And suppose that your Raspberry Pi 3 is reachable via 192.168.1.109<\/strong>, create the following content inside Save the configuration file when you had completed filling up your details.<\/p>\n Once you had created the initial configuration file, run the following commands to run Taiga backend temporarily:<\/p>\n Open up another SSH session to your raspberry pi:<\/p>\n And type the following command:<\/p>\n If taiga-back is setup correctly, you should be able to see a JSON representing the list of endpoints at the url: http:\/\/localhost:8000\/api\/v1\/.<\/p>\n Once you had verified that taiga-back is setup correctly, go back to the SSH session that you run Taiga backend from. Stop running Taiga backend by pressing CONTROL-C.<\/p>\n After setting up Taiga backend, proceed on to setup Taiga frontend.<\/p>\n Run the following commands to download a copy of Taiga frontend:<\/p>\n After the commands had completed, create the configuration file from the sample configuration:<\/p>\n Use And supposing that your Raspberry Pi 3 is reachable via 192.168.1.109<\/strong>, edit Once you had setup Taiga frontend on your Raspberry Pi 3, you may choose to setup Taiga events which is an optional component.<\/p>\n Taiga-events is the Taiga websocket server, it allows taiga frontend to show realtime changes in the backlog, taskboard, kanban and issues listing. Taiga events uses RabbitMQ as the message broker. <\/p>\n Run the following commands to get a copy of Taiga events:<\/p>\n Run the following commands to install Node.js<\/a> on your Raspberry Pi 3:<\/p>\n Run the following commands to install the JavaScript dependencies that is required to run Taiga events:<\/p>\n Run the following command to base the configurations for Taiga events from the given sample:<\/p>\n After the copy command completes, use nano to open up And update the contents with your RabbitMQ URI and the secret key. Your Note: The 'secret' in your Supervisor<\/a> is a process control system that can help keep Taiga backend and Taiga events running on your Raspberry Pi 3. <\/p>\n Once we had the codes for Taiga components and Taiga events in our Raspberry Pi 3, we can proceed to configure Supervisor to run them.<\/p>\n We first create a bash script for Supervisor to run Taiga backend. Inside the bash script, we will instruct gunicorn to start Taiga backend for us.<\/p>\n First create a file at taiga home directory:<\/p>\n And inside Once you had saved After you had made And inside Next up, proceed to configure Supervisor to run Taiga events. To do so, create a supervisor configuration file at And inside After you had created the Supervisor configurations, restart Supervisor to get it to run Taiga backend and Taiga events:<\/p>\n The next step is configure Nginx as a reverse proxy server<\/a> for Taiga frontend, Taiga backend and Taiga events. To do so, remove And create Inside Save the file and restart Nginx:<\/p>\n Once you had restarted Nginx, you can use the browser on your home computer to access your Taiga installation on your Raspberry Pi 3.<\/p>\n Suppose that your Raspberry Pi 3 is reachable from your home computer via You should see the following screen:<\/p>\n Remember that we had created an administrator account with login username admin<\/strong> with password 123123<\/strong>. This is not safe as anybody who read this post can get administrator access to your Taiga installation.<\/p>\n To change the password of the administrator account, click on the \"login\" button at the top right corner to get to the login page. Enter the default administrator account credentials in the login page:<\/p>\n And click on the \"LOGIN\" button. <\/p>\n Once you had logged into Taiga successfully, click on the \"Administrator\" button at the top, and then the \"EDIT BIO\" button at the right. You will see the \"USER SETTINGS\" page:<\/p>\n Click on the \"CHANGE PASSWORD\" button on the left to access the \"CHANGE PASSWORD\" page:<\/p>\n Enter the relevant input and click on the \"SAVE\" button. <\/p>\n Notice that the profile photo is broken. To correct that, go to the \"USER SETTINGS\" page by clicking on the \"USER PROFILE\" tab at the left. In the \"USER SETTINGS\" page, click on the \"CHANGE PHOTO\" button to choose a picture from your computer as the new profile picture.<\/p>\n At this point in time, you had setup a Taiga installation on your Raspberry Pi 3 that can only be accessed from within your home network. <\/p>\n If you want to be able to access your Taiga installation from outside your home network, there are more configurations to be done.<\/p>\n As mentioned in an earlier post on how to host multiple websites from home<\/a>, you will need the following pieces for enabling your Taiga installation to be accessed from outside your home network via HTTPS with Let's Encrypt browser-trusted certificate:<\/p>\nRecommended hardware list<\/h2>\n
\n
Setting up Raspbian Stretch Lite on Raspberry Pi 3 to run Python 3 applications<\/h2>\n
\n
Installing other dependency packages for Taiga<\/h2>\n
\r\nsudo apt-get update\r\nsudo apt-get install -y build-essential binutils-doc autoconf flex bison libjpeg-dev\r\nsudo apt-get install -y libfreetype6-dev zlib1g-dev libzmq3-dev libgdbm-dev libncurses5-dev\r\nsudo apt-get install -y automake libtool libffi-dev curl git tmux gettext\r\nsudo apt-get install -y rabbitmq-server redis-server\r\nsudo apt-get install -y nginx supervisor\r\nsudo apt-get install -y postgresql postgresql-contrib\r\nsudo apt-get install -y postgresql-doc postgresql-server-dev-9.6\r\nsudo apt-get install -y python-dev\r\nsudo apt-get install -y libxml2-dev libxslt-dev\r\nsudo apt-get install -y libssl-dev libffi-dev\r\nsudo apt-get install -y libopenjp2-7-dev\r\n<\/pre>\n
Creating a system user taiga, giving it root permissions and switch the current user with taiga<\/h2>\n
taiga<\/code><\/strong>, give it root permissions and switch the current user to taiga:<\/p>\n\r\nsudo adduser taiga\r\nsudo adduser taiga sudo\r\nsudo su taiga\r\ncd ~\r\n<\/pre>\n
taiga<\/code> user to proceed with the rest of this guide.<\/p>\nSetting up PostgreSQL with the initial user and database<\/h2>\n
taiga<\/code> user, run the following commands to setup PostgreSQL<\/a> for the Taiga project management platform:<\/p>\n\r\nsudo -u postgres createuser taiga\r\nsudo -u postgres createdb taiga -O taiga --encoding='utf-8' --locale=en_US.utf8 --template=template0\r\n<\/pre>\n
Creating a user named taiga, and a virtual host for RabbitMQ<\/h2>\n
taiga-events<\/code>:<\/p>\n\r\nsudo rabbitmqctl add_user taiga PASSWORD_FOR_EVENTS\r\nsudo rabbitmqctl add_vhost taiga\r\nsudo rabbitmqctl set_permissions -p taiga taiga ".*" ".*" ".*"\r\n<\/pre>\n
Creating the logs folder<\/h2>\n
logs<\/code> directory for the various Taiga components to write logs to: <\/p>\n\r\nmkdir -p ~\/logs\r\n<\/pre>\n
Setting up Taiga backend<\/h2>\n
logs<\/code> directory, we can then proceed to setup Taiga backend.<\/p>\nDownloading a copy of Taiga backend<\/h3>\n
\r\ncd ~\r\ngit clone https:\/\/github.com\/taigaio\/taiga-back.git taiga-back\r\ncd taiga-back\r\ngit checkout stable\r\n<\/pre>\n
Creating a virtual environment for Taiga backend<\/h3>\n
\r\ncd ~\r\nvirtualenv -p python3 taiga-back_env\r\n<\/pre>\n
Installing Taiga backend dependencies in virtual environment<\/h3>\n
\r\ncd ~\r\nsource taiga-back_env\/bin\/activate\r\ncd taiga-back\r\npip install -r requirements.txt\r\n<\/pre>\n
Populating the database with initial basic data<\/h3>\n
\r\npython manage.py migrate --noinput\r\npython manage.py loaddata initial_user\r\npython manage.py loaddata initial_project_templates\r\npython manage.py compilemessages\r\npython manage.py collectstatic --noinput\r\n<\/pre>\n
Creating the initial configuration file<\/h3>\n
\r\nnano ~\/taiga-back\/settings\/local.py\r\n<\/pre>\n
local.py<\/code>:<\/p>\n\r\nfrom .common import *\r\n\r\nMEDIA_URL = "http:\/\/192.168.1.109\/media\/"\r\nSTATIC_URL = "http:\/\/192.168.1.109\/static\/"\r\nSITES["front"]["scheme"] = "http"\r\nSITES["front"]["domain"] = "192.168.1.109"\r\n\r\nSECRET_KEY = "theveryultratopsecretkey"\r\n\r\nDEBUG = False\r\nPUBLIC_REGISTER_ENABLED = False\r\n\r\nDEFAULT_FROM_EMAIL = "no-reply@192.168.1.109"\r\nSERVER_EMAIL = DEFAULT_FROM_EMAIL\r\n\r\n#CELERY_ENABLED = True\r\n\r\nEVENTS_PUSH_BACKEND = "taiga.events.backends.rabbitmq.EventsPushBackend"\r\nEVENTS_PUSH_BACKEND_OPTIONS = {"url": "amqp:\/\/taiga:PASSWORD_FOR_EVENTS@localhost:5672\/taiga"}\r\n\r\n# Uncomment and populate with proper connection parameters\r\n# for enable email sending. EMAIL_HOST_USER should end by @domain.tld\r\n#EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend"\r\n#EMAIL_USE_TLS = False\r\n#EMAIL_HOST = "localhost"\r\n#EMAIL_HOST_USER = ""\r\n#EMAIL_HOST_PASSWORD = ""\r\n#EMAIL_PORT = 25\r\n\r\n# Uncomment and populate with proper connection parameters\r\n# for enable github login\/singin.\r\n#GITHUB_API_CLIENT_ID = "yourgithubclientid"\r\n#GITHUB_API_CLIENT_SECRET = "yourgithubclientsecret"\r\n<\/pre>\nVerifying Taiga backend installation<\/h3>\n
\r\nsource ~\/taiga-back_env\/bin\/activate\r\npython ~\/taiga-back\/manage.py runserver\r\n<\/pre>\n
\r\nssh pi@192.168.1.109\r\n<\/pre>\n
\r\ncurl -0 http:\/\/localhost:8000\/api\/v1\/ \r\n<\/pre>\n
Setting up Taiga frontend<\/h2>\n
Downloading a copy of Taiga frontend<\/h3>\n
\r\ncd ~\r\ngit clone https:\/\/github.com\/taigaio\/taiga-front-dist.git taiga-front-dist\r\ncd taiga-front-dist\r\ngit checkout stable\r\n<\/pre>\n
\r\ncp ~\/taiga-front-dist\/dist\/conf.example.json ~\/taiga-front-dist\/dist\/conf.json\r\n<\/pre>\n
nano<\/code> to open up conf.json<\/code>:<\/p>\n\r\nsudo nano ~\/taiga-front-dist\/dist\/conf.json\r\n<\/pre>\n
conf.json<\/code> to look like the following:<\/p>\n\r\n{\r\n "api": "http:\/\/192.168.1.109\/api\/v1\/",\r\n "eventsUrl": "ws:\/\/192.168.1.109\/events",\r\n "eventsMaxMissedHeartbeats": 5,\r\n "eventsHeartbeatIntervalTime": 60000,\r\n "eventsReconnectTryInterval": 10000,\r\n "debug": true,\r\n "debugInfo": false,\r\n "defaultLanguage": "en",\r\n "themes": ["taiga"],\r\n "defaultTheme": "taiga",\r\n "publicRegisterEnabled": false,\r\n "feedbackEnabled": true,\r\n "supportUrl": "https:\/\/tree.taiga.io\/support",\r\n "privacyPolicyUrl": null,\r\n "termsOfServiceUrl": null,\r\n "maxUploadFileSize": null,\r\n "contribPlugins": [],\r\n "tribeHost": null,\r\n "importers": [],\r\n "gravatar": true\r\n}\r\n<\/pre>\nSetting up Taiga events<\/h2>\n
Downloading a copy of Taiga events<\/h3>\n
\r\ncd ~\r\ngit clone https:\/\/github.com\/taigaio\/taiga-events.git taiga-events\r\ncd taiga-events\r\n<\/pre>\n
Installing nodejs<\/h3>\n
\r\ncurl -sL https:\/\/deb.nodesource.com\/setup_6.x | sudo -E bash -\r\nsudo apt-get install -y nodejs\r\n<\/pre>\n
Installing JavaScript dependencies<\/h3>\n
\r\nnpm install\r\nsudo npm install -g coffee-script\r\n<\/pre>\n
Creating the configuration for Taiga events<\/h3>\n
\r\ncp config.example.json config.json\r\n<\/pre>\n
config.json<\/code>:<\/p>\n\r\nnano config.json\r\n<\/pre>\n
config.json<\/code> file should look like this:<\/p>\n\r\n{\r\n "url": "amqp:\/\/taiga:PASSWORD_FOR_EVENTS@localhost:5672\/taiga",\r\n "secret": "theveryultratopsecretkey",\r\n "webSocketServer": {\r\n "port": 8888\r\n }\r\n}\r\n<\/pre>\nconfig.json<\/code> must be the same as the \"SECRET_KEY\" in ~\/taiga-back\/settings\/local.py<\/code>.<\/strong><\/p>\nConfiguring Supervisor to run Taiga backend and Taiga events<\/h2>\n
Configuring Supervisor to run Taiga backend<\/h3>\n
\r\nnano ~\/run_taiga_backend.sh\r\n<\/pre>\n
taiga_backend.sh<\/code>, create the following content:<\/p>\n\r\n#!\/bin\/bash\r\n\r\nsource taiga-back_env\/bin\/activate\r\ngunicorn -w 3 -t 60 --pythonpath=.\/taiga-back -b 127.0.0.1:8001 taiga-back.taiga.wsgi\r\ndeactivate\r\n<\/pre>\n
taiga_backend.sh<\/code>, run the following command to make it executable by the taiga user:<\/p>\n\r\nchmod u+x ~\/run_taiga_backend.sh\r\n<\/pre>\n
run_taiga_backend.sh<\/code> executable by the taiga user, create a supervisor configuration file at \/etc\/supervisor\/conf.d\/taiga-back.conf<\/code>:<\/p>\n\r\nsudo nano \/etc\/supervisor\/conf.d\/taiga-back.conf\r\n<\/pre>\n
taiga-back.conf<\/code> create the following content:<\/p>\n\r\n[program:taiga-back]\r\ndirectory=\/home\/taiga\r\ncommand=\/bin\/bash -E -c .\/run_taiga_backend.sh\r\nautostart=true\r\nautorestart=true\r\nstopsignal=INT\r\nstopasgroup=true\r\nkillasgroup=true\r\nstdout_logfile=\/home\/taiga\/logs\/taiga-back.stdout.log\r\nstderr_logfile=\/home\/taiga\/logs\/taiga-back.stderr.log\r\nuser=taiga\r\n<\/pre>\n
Configuring Supervisor to run Taiga events<\/h3>\n
\/etc\/supervisor\/conf.d\/taiga-events.conf<\/code>:<\/p>\n\r\nsudo nano \/etc\/supervisor\/conf.d\/taiga-events.conf\r\n<\/pre>\n
\/etc\/supervisor\/conf.d\/taiga-events.conf<\/code>, create the following content:<\/p>\n\r\n[program:taiga-events]\r\ndirectory=\/home\/taiga\/taiga-events\r\ncommand=\/usr\/bin\/coffee index.coffee \r\nautostart=true\r\nautorestart=true\r\nstopsignal=INT\r\nstopasgroup=true\r\nkillasgroup=true\r\nstdout_logfile=\/home\/taiga\/logs\/taiga-events.stdout.log\r\nstderr_logfile=\/home\/taiga\/logs\/taiga-events.stderr.log\r\nuser=taiga \r\n<\/pre>\n
Restarting Supervisor<\/h3>\n
\r\nsudo systemctl restart supervisor.service\r\n<\/pre>\n
Configuring Nginx to serve Taiga frontend, Taiga backend and Taiga events<\/h2>\n
\/etc\/nginx\/sites-enabled\/default<\/code>:<\/p>\n\r\nsudo rm \/etc\/nginx\/sites-enabled\/default\r\n<\/pre>\n
\/etc\/nginx\/sites-enabled\/taiga.conf<\/code>:<\/p>\n\r\nsudo nano \/etc\/nginx\/sites-enabled\/taiga.conf\r\n<\/pre>\n
taiga.conf<\/code>, create the following content:<\/p>\n\r\nserver {\r\n listen 80 default_server;\r\n server_name _;\r\n\r\n large_client_header_buffers 4 32k;\r\n client_max_body_size 50M;\r\n charset utf-8;\r\n\r\n access_log \/home\/taiga\/logs\/nginx.access.log;\r\n error_log \/home\/taiga\/logs\/nginx.error.log;\r\n\r\n # Frontend\r\n location \/ {\r\n root \/home\/taiga\/taiga-front-dist\/dist\/;\r\n try_files $uri $uri\/ \/index.html;\r\n }\r\n\r\n # Backend\r\n location \/api {\r\n include proxy_params;\r\n proxy_set_header X-Scheme $scheme;\r\n proxy_pass http:\/\/127.0.0.1:8001\/api;\r\n proxy_redirect off;\r\n }\r\n\r\n # Django admin access (\/admin\/)\r\n location \/admin {\r\n include proxy_params;\r\n proxy_set_header X-Scheme $scheme;\r\n proxy_pass http:\/\/127.0.0.1:8001$request_uri;\r\n proxy_redirect off;\r\n }\r\n\r\n # Static files\r\n location \/static {\r\n alias \/home\/taiga\/taiga-back\/static;\r\n }\r\n\r\n # Media files\r\n location \/media {\r\n alias \/home\/taiga\/taiga-back\/media;\r\n }\r\n\r\n # Taiga-events\r\n location \/events {\r\n proxy_pass http:\/\/127.0.0.1:8888\/events;\r\n proxy_http_version 1.1;\r\n proxy_set_header Upgrade $http_upgrade;\r\n proxy_set_header Connection "upgrade";\r\n proxy_connect_timeout 7d;\r\n proxy_send_timeout 7d;\r\n proxy_read_timeout 7d;\r\n }\r\n}\r\n<\/pre>\n\r\nsudo systemctl restart nginx.service\r\n<\/pre>\n
Accessing Taiga from your home computer<\/h2>\n
192.168.1.109<\/code><\/strong>, enter http:\/\/192.168.1.109<\/strong> in the location bar.<\/p>\n![\"Taiga](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/taiga-home-page-via-192.168.1.109.gif\")
<\/p>\nChanging the default password of the administrator account<\/h2>\n
![\"Taiga](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/taiga-login-page-with-admin-credentials-supplied.jpg\")
<\/p>\n![\"Taiga](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/taiga-user-settings-screen.jpg\")
<\/p>\n![\"Taiga](\"https:\/\/www.techcoil.com\/blog\/wp-content\/uploads\/taiga-change-password-screen.jpg\")
<\/p>\nChanging profile photo<\/h2>\n
Configuring your Taiga installation to be accessed from outside your home network via HTTPS with Let's Encrypt certificate<\/h2>\n
Pre-requisites<\/h3>\n
\n
Installing CertBot<\/h3>\n