Difference between revisions of "Taiga"

From Organic Design wiki
(Undo revision 128633 by Saul (talk))
(Tag: Undo)
(Install: Updated layout and instructions.)
Line 10: Line 10:
 
</source>
 
</source>
  
Replace every instance of these with passwords in '''docker-compose.yml''' and '''docker-compose-inits.yml''':
+
Replace every instance of these with passwords in '''docker-compose.yml''' and '''docker-compose-inits.yml'''.
  
* POSTGRES_PASSWORD
+
'''Important''': do not include symbols in the passwords or else you may get some very strange errors.
* TAIGA_SECRET_KEY
+
<source>
* RABBITMQ_PASS
+
POSTGRES_PASSWORD
 +
TAIGA_SECRET_KEY
 +
RABBITMQ_PASS
 +
</source>
  
 
Edit these values to match your setup:
 
Edit these values to match your setup:
 
+
<source>
* TAIGA_SITES_SCHEME: http
+
TAIGA_SITES_SCHEME: http
* TAIGA_SITES_DOMAIN: example.com
+
TAIGA_SITES_DOMAIN: example.com
* TAIGA_URL: "http://example.com"
+
TAIGA_URL: "http://example.com"
* TAIGA_WEBSOCKETS_URL: "ws://example.com"
+
TAIGA_WEBSOCKETS_URL: "ws://example.com"
 +
</source>
  
 
Then run:
 
Then run:
 
<source lang="bash">
 
<source lang="bash">
 
./launch-taiga.sh # Or ./launch-all.sh if you want penpot too
 
./launch-taiga.sh # Or ./launch-all.sh if you want penpot too
# Wait a couple of minutes AFTER the command has FINISHED
+
# Wait a couple of minutes AFTER the command has FINISHED then run it again.
 +
./launch-taiga.sh
 +
# Check that the back service has finished booting (May take 5mins) :
 +
docker logs taiga-docker_taiga-back_1
 +
</source>
 +
 
 +
You should have observed the following on the last command:
 +
<source>
 +
Applied <THINGS>
 +
Give permission to taiga:taiga
 +
Listening at: http://0.0.0.0:8000 (1)
 +
<Booted 3 service workers>
 +
</source>
 +
 
 +
Once you see the service workers are booted you can create the super user:
 +
 
 +
<source lang="bash">
 
./taiga-manage.sh createsuperuser
 
./taiga-manage.sh createsuperuser
# If this command has errors and fails and says something about migrating either wait longer or run:
 
./taiga-manage.sh migrate
 
 
</source>
 
</source>
 
If you need to change the Taiga configuration just run the '''launch-taiga.sh'''/'''launch-all.sh''' again.
 
  
  
Line 39: Line 55:
 
listen 80;
 
listen 80;
 
</source>
 
</source>
 +
 +
=== Updating Configuration ===
 +
If you need to change the Taiga configuration just run the '''launch-taiga.sh'''/'''launch-all.sh''' again.
 +
 +
 +
If you need to change config details that involve the setup you may need to nuke the volumes:
 +
<source lang="bash">
 +
docker-compose down -v
 +
</source>
 +
 
=== https ===
 
=== https ===
 
Https can be a bit tricky to setup at first but just make sure to make all of these listed changes and it should work:
 
Https can be a bit tricky to setup at first but just make sure to make all of these listed changes and it should work:

Revision as of 22:25, 14 April 2021

Install

The documentation is fairly good at describing what to do but here is a quick set guide.

First check you have git, docker and docker-compose installed at the versions it recommends.

git clone https://github.com/taigaio/taiga-docker
cd taia-docker
git checkout stable

Replace every instance of these with passwords in docker-compose.yml and docker-compose-inits.yml.

Important: do not include symbols in the passwords or else you may get some very strange errors.

POSTGRES_PASSWORD
TAIGA_SECRET_KEY
RABBITMQ_PASS

Edit these values to match your setup:

TAIGA_SITES_SCHEME: http
TAIGA_SITES_DOMAIN: example.com
TAIGA_URL: "http://example.com"
TAIGA_WEBSOCKETS_URL: "ws://example.com"

Then run:

./launch-taiga.sh # Or ./launch-all.sh if you want penpot too
# Wait a couple of minutes AFTER the command has FINISHED then run it again.
./launch-taiga.sh
# Check that the back service has finished booting (May take 5mins) :
docker logs taiga-docker_taiga-back_1

You should have observed the following on the last command:

Applied <THINGS>
Give permission to taiga:taiga
Listening at: http://0.0.0.0:8000 (1)
<Booted 3 service workers>

Once you see the service workers are booted you can create the super user:

./taiga-manage.sh createsuperuser


Make sure you set up the reverse proxy exactly as the documentation says just don't forget to add a listen line:

listen 80;

Updating Configuration

If you need to change the Taiga configuration just run the launch-taiga.sh/launch-all.sh again.


If you need to change config details that involve the setup you may need to nuke the volumes:

docker-compose down -v

https

Https can be a bit tricky to setup at first but just make sure to make all of these listed changes and it should work:

First ensure the webserver is listening for https or port 443 - do not change the proxy target!

Then in docker-compose.yml make the following edits:

  • TAIGA_SITES_SCHEME: "https"
  • TAIGA_URL: "https://example.com"
  • TAIGA_WEBSOCKETS_URL: "wss://taiga.organicdesign.fund"

There is no need to change the port at the bottom of the file.