{"id":50735140,"url":"https://github.com/eteriall/taiga-docker-cob","last_synced_at":"2026-06-10T12:42:50.751Z","repository":{"id":298727784,"uuid":"983330297","full_name":"eteriall/taiga-docker-cob","owner":"eteriall","description":null,"archived":false,"fork":false,"pushed_at":"2025-06-12T14:06:27.000Z","size":4502,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2026-06-10T12:42:48.767Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"CoffeeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/eteriall.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS.rst","dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2025-05-14T08:15:51.000Z","updated_at":"2025-06-12T14:06:45.000Z","dependencies_parsed_at":"2025-06-12T15:36:34.938Z","dependency_job_id":null,"html_url":"https://github.com/eteriall/taiga-docker-cob","commit_stats":null,"previous_names":["eteriall/taiga-docker-cob"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/eteriall/taiga-docker-cob","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/eteriall%2Ftaiga-docker-cob","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/eteriall%2Ftaiga-docker-cob/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/eteriall%2Ftaiga-docker-cob/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/eteriall%2Ftaiga-docker-cob/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/eteriall","download_url":"https://codeload.github.com/eteriall/taiga-docker-cob/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/eteriall%2Ftaiga-docker-cob/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":34153483,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-10T02:00:07.152Z","response_time":89,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-06-10T12:42:49.686Z","updated_at":"2026-06-10T12:42:50.745Z","avatar_url":"https://github.com/eteriall.png","language":"CoffeeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Taiga Docker\n\n| :exclamation: | We recently announced Taiga plans for the future and they greatly affect how we manage this repository and the current Taiga 6 release. Check it [here](https://blog.taiga.io/announcing_taiganext.html).    |\n|---------------|:----|\n\n| :information_source: | If you're already using taiga-docker, follow this [migration guide](https://docs.taiga.io/upgrades-docker-migrate.html) to use the new `.env` based deployment. |\n|---------------|:----|\n\n\u003e **Note:**\n\u003e You can access the [older docker installation guide](https://docs.taiga.io/setup-production.old.html#setup-prod-with-docker-old) for documentation purposes, intended just for earlier versions of Taiga (prior to ver. 6.6.0)\n\n\n## Getting Started\n\nThis section intends to explain how to get Taiga up and running in a simple two steps, using **docker** and **docker compose**.\n\nIf you don't have docker installed, please follow installation instructions from [docker.com](https://docs.docker.com/engine/install/) (**version 19.03.0+**)\n\nAdditionally, it's necessary to have familiarity with Docker, docker compose and Docker repositories.\n\n\u003e **Note**\n\u003e branch `stable` should be used to deploy Taiga in production and `main` branch for development purposes.\n\n### Start the application\n\n```sh\n$ ./launch-all.sh\n```\n\nAfter some instants, when the application is started you can proceed to create the superuser with the following script:\n\n```sh\n$ ./taiga-manage.sh createsuperuser\n```\n\nThe `taiga-manage.sh` script lets launch manage.py commands on the\nback instance:\n\n```sh\n$ ./taiga-manage.sh [COMMAND]\n```\n\nIf you're testing it in your own machine, you can access the application in **http://localhost:9000**. If you're deploying in a server, you'll need to configure hosts and nginx as described later.\n\n![Taiga screenshot](imgs/taiga.jpg)\n\nAs **EXTRA**: the default `launch-all.sh` script comes with [penpot](https://penpot.app), the open-source solution for design and prototyping. The default access for the penpot application is **http://localhost:9001**\n\nIt's developed by the same team behind Taiga. If you want to give it a try, you can go to [penpot's github](https://github.com/penpot/penpot) or the [help center](https://help.penpot.app/technical-guide/configuration/) to review its own configuration variables.\n\n![Penpot screenshot](imgs/penpot.jpg)\n\nAnd finally if you just want to launch Taiga standalone, you can use the `launch-taiga.sh` script instead of the `launch-all.sh`.\n\n## Documentation\n\nCurrently, we have authored three main documentation hubs:\n\n- **[API](https://docs.taiga.io/api.html)**: Our API documentation and reference for developing from Taiga API.\n- **[Documentation](https://docs.taiga.io/)**: If you need to install Taiga on your own server, this is the place to find some guides.\n- **[Taiga Community](https://community.taiga.io/)**: This page is intended to be the support reference page for the users.\n\n## Bug reports\n\nIf you **find a bug** in Taiga you can always report it:\n\n- in [Taiga issues](https://tree.taiga.io/project/taiga/issues). **This is the preferred way**\n- in [Github issues](https://github.com/taigaio/taiga-docker/issues)\n- send us a mail to support@taiga.io if is a bug related to [tree.taiga.io](https://tree.taiga.io)\n- send us a mail to security@taiga.io if is a **security bug**\n\nOne of our fellow Taiga developers will search, find and hunt it as soon as possible.\n\nPlease, before reporting a bug, write down how can we reproduce it, your operating system, your browser and version, and if it's possible, a screenshot. Sometimes it takes less time to fix a bug if the developer knows how to find it.\n\n## Community\n\nIf you **need help to setup Taiga**, want to **talk about some cool enhancemnt** or you have **some questions**, please go to [Taiga community](https://community.taiga.io/).\n\nIf you want to be up to date about announcements of releases, important changes and so on, you can subscribe to our newsletter (you will find it by scrolling down at [https://taiga.io](https://www.taiga.io/)) and follow [@taigaio](https://twitter.com/taigaio) on Twitter.\n\n## Contribute to Taiga\n\nThere are many different ways to contribute to Taiga's platform, from patches, to documentation and UI enhancements, just find the one that best fits with your skills. Check out our detailed [contribution guide](https://community.taiga.io/t/how-can-i-contribute/159#code-patches-enhacements-3).\n\n## Code of Conduct\n\nHelp us keep the Taiga Community open and inclusive. Please read and follow our [Code of Conduct](https://github.com/taigaio/code-of-conduct/blob/main/CODE_OF_CONDUCT.md).\n\n## License\n\nEvery code patch accepted in Taiga codebase is licensed under [MPL 2.0](LICENSE). You must be careful to not include any code that can not be licensed under this license.\n\nPlease read carefully [our license](LICENSE) and ask us if you have any questions as well as the [Contribution policy](https://github.com/taigaio/taiga-docker/blob/main/CONTRIBUTING.md).\n\n## Configuration\n\nWe've exposed the **Basic configuration** settings in Taiga to an `.env` file. We strongly recommend you to change it, or at least review its content, to avoid using the default values.\n\nBoth `docker-compose.yml` and `docker-compose-inits.yml` will read from this file to populate their environment variables, so, initially you don't need to change them. Edit these files just in case you require to enable **Additional customization**, or an **Advanced configuration**.\n\nRefer to these sections for further information.\n\n## Basic Configuration\n\nYou will find basic **configuration variables** in the `.env` file. As stated before, we encourage you to edit these values, especially those affecting the security.\n\n### Database settings\n\nThese vars are used to create the database for Taiga and connect to it.\n\n```bash\nPOSTGRES_USER=taiga  # user to connect to PostgreSQL\nPOSTGRES_PASSWORD=taiga  # database user's password\n```\n\n### URLs settings\n\nThese vars set where your Taiga instance should be served, and the security protocols to use in the communication layer.\n\n```bash\nTAIGA_SCHEME=http  # serve Taiga using \"http\" or \"https\" (secured) connection\nTAIGA_DOMAIN=localhost:9000  # Taiga's base URL\nSUBPATH=\"\"  # it'll be appended to the TAIGA_DOMAIN (use either \"\" or a \"/subpath\")\nWEBSOCKETS_SCHEME=ws  # events connection protocol (use either \"ws\" or \"wss\")\n```\n\nThe default configuration assumes Taiga is being served in a **subdomain**. For example:\n\n```bash\nTAIGA_SCHEME=https\nTAIGA_DOMAIN=taiga.mycompany.com\nSUBPATH=\"\"\nWEBSOCKETS_SCHEME=wss\n```\n\nIf Taiga is being served in a **subpath**, instead of a subdomain, the configuration should be something like this:\n\n```bash\nTAIGA_SCHEME=https\nTAIGA_DOMAIN=mycompany.com\nSUBPATH=\"/taiga\"\nWEBSOCKETS_SCHEME=wss\n```\n\n### Secret Key settings\n\nThis variable allows you to set the secret key in Taiga, used in the cryptographic signing.\n\n```bash\nSECRET_KEY=\"taiga-secret-key\"  # Please, change it to an unpredictable value!\n```\n\n### Email Settings\n\nBy default, emails will be printed in the standard output (`EMAIL_BACKEND=console`). If you have your own SMTP service, change it to `EMAIL_BACKEND=smtp` and configure the rest of these variables with the values supplied by your SMTP provider:\n\n```bash\nEMAIL_BACKEND=console  # use an SMTP server or display the emails in the console (either \"smtp\" or \"console\")\nEMAIL_HOST=smtp.host.example.com  # SMTP server address\nEMAIL_PORT=587   # default SMTP port\nEMAIL_HOST_USER=user  # user to connect the SMTP server\nEMAIL_HOST_PASSWORD=password  # SMTP user's password\nEMAIL_DEFAULT_FROM=changeme@example.com  # email address for the automated emails\n\n# EMAIL_USE_TLS/EMAIL_USE_SSL are mutually exclusive (only set one of those to True)\nEMAIL_USE_TLS=True  # use TLS (secure) connection with the SMTP server\nEMAIL_USE_SSL=False  # use implicit TLS (secure) connection with the SMTP server\n```\n\n### Queue manager settings\n\nThese variables are used to leave messages in the rabbitmq services.\n\n```bash\nRABBITMQ_USER=taiga  # user to connect to RabbitMQ\nRABBITMQ_PASS=taiga  # RabbitMQ user's password\nRABBITMQ_VHOST=taiga  # RabbitMQ container name\nRABBITMQ_ERLANG_COOKIE=secret-erlang-cookie  # unique value shared by any connected instance of RabbitMQ\n```\n\n### Attachments settings\n\nYou can configure how long the attachments will be accessible by changing the token expiration timer. After that amount of seconds the token will expire, but you can always get a new attachment url with an active token.\n\n```bash\nATTACHMENTS_MAX_AGE=360  # token expiration date (in seconds)\n```\n\n### Telemetry Settings\n\nTelemetry anonymous data is collected in order to learn about the use of Taiga and improve the platform based on real scenarios. You may want to enable this to help us shape future Taiga.\n\n```bash\nENABLE_TELEMETRY=True\n```\n\nYou can opt out by setting this variable to False. By default, it's True.\n\n## Additional customization\n\nAll these customization options are by default disabled and require you to edit `docker-compose.yml`.\n\nYou should add the corresponding environment variables in the proper services (or in `\u0026default-back-environment` group) with a valid value in order to enable them. Please, do not modify it unless you know what you’re doing.\n\n### Session cookies in Django Admin\n\nTaiga doesn't use session cookies in its API as it stateless. However, the Django Admin (`/admin/`) uses session cookie for authentication. By default, Taiga is configured to work behind HTTPS. If you're using HTTP (despite the strong recommendations against it), you'll need to configure the following environment variables so you can access the Admin:\n\nAdd to `\u0026default-back-environment` environments\n```yml\nSESSION_COOKIE_SECURE: \"False\"\nCSRF_COOKIE_SECURE: \"False\"\n```\n\nMore info about those variables can be found [here](https://docs.djangoproject.com/en/3.1/ref/settings/#csrf-cookie-secure).\n\n### Public registration\n\nPublic registration is disabled by default. If you want to allow a public register, you have to enable public registration on both, frontend and backend.\n\n\u003e **Note**\n\u003e Be careful with the upper and lower case in these settiings. We will use 'True' for the backend and 'true' for the frontend (this is not a typo, otherwise it won't work).\n\n\nAdd to `\u0026default-back-environment` environments\n```yml\nPUBLIC_REGISTER_ENABLED: \"True\"\n```\n\nAdd to `taiga-front` service environments\n```yml\nPUBLIC_REGISTER_ENABLED: \"true\"\n```\n\n\u003e **Important**:\n\u003e\n\u003e Taiga (in its default configuration) disables both Gitlab or Github oauth buttons whenever the public registration option hasn't been activated. To be able to use Github/Gitlab login/registration, make sure you have public registration activated on your Taiga instance.\n\n### GitHub OAuth login\n\nUsed for login with Github. This feature is disabled by default.\n\nFollow the documentation ([GitHub - Creating an OAuth App](https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/creating-an-oauth-app)) in Github, when save application Github displays the ID and Secret.\n\n\u003e **Note** \n\u003e Be careful with the upper and lower case in these settiings. We will use 'True' for the backend and 'true' for the frontend (this is not a typo, otherwise it won't work).\n\n\u003e **Note**\n\u003e `GITHUB_API_CLIENT_ID / GITHUB_CLIENT_ID` should have the same value.\n\n\nAdd to `\u0026default-back-environment` environments\n```yml\nENABLE_GITHUB_AUTH: \"True\"\nGITHUB_API_CLIENT_ID: \"github-client-id\"\nGITHUB_API_CLIENT_SECRET: \"github-client-secret\"\nPUBLIC_REGISTER_ENABLED: \"True\"\n```\n\nAdd to `taiga-front` service environments\n```yml\nENABLE_GITHUB_AUTH: \"true\"\nGITHUB_CLIENT_ID: \"github-client-id\"\nPUBLIC_REGISTER_ENABLED: \"true\"\n````\n\n### Gitlab OAuth login\n\nUsed for login with GitLab. This feature is disabled by default.\n\nFollow the documentation ([Configure GitLab as an OAuth 2.0 authentication identity provider](https://docs.gitlab.com/ee/integration/oauth_provider.html)) in Gitlab to get the _gitlab-client-id_ and the _gitlab-client-secret_.\n\n\u003e **Note** \n\u003e Be careful with the upper and lower case in these settiings. We will use 'True' for the backend and 'true' for the frontend (this is not a typo, otherwise it won't work).\n\n\u003e **Note** \n\u003e `GITLAB_API_CLIENT_ID / GITLAB_CLIENT_ID` and `GITLAB_URL` should have the same value.\n\nAdd to `\u0026default-back-environment` environments\n```yml\nENABLE_GITLAB_AUTH: \"True\"\nGITLAB_API_CLIENT_ID: \"gitlab-client-id\"\nGITLAB_API_CLIENT_SECRET: \"gitlab-client-secret\"\nGITLAB_URL: \"gitlab-url\"\nPUBLIC_REGISTER_ENABLED: \"True\"\n```\n\nAdd to `taiga-front` service environments\n```yml\nENABLE_GITLAB_AUTH: \"true\"\nGITLAB_CLIENT_ID: \"gitlab-client-id\"\nGITLAB_URL: \"gitlab-url\"\nPUBLIC_REGISTER_ENABLED: \"true\"\n```\n\n### Slack integration\n\nEnable Slack integration in your Taiga instance. This feature is disabled by default.\n\n\u003e **Note** \n\u003e Be careful with the upper and lower case in these settiings. We will use 'True' for the backend and 'true' for the frontend (this is not a typo, otherwise it won't work).\n\nAdd to `\u0026default-back-environment` environments\n```yml\nENABLE_SLACK: \"True\"\n```\n\nAdd to `taiga-front` service environments\n```yml\nENABLE_SLACK: \"true\"\n```\n\n### GitHub importer\n\nActivating this feature, you will be able to import projects from GitHub.\n\nFollow this documentation ([GitHub - Creating an OAuth App](https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/creating-an-oauth-app)) to obtain the _client id_ and the _client secret_ from GitHun.\n\n\u003e **Note**\n\u003e Be careful with the upper and lower case in these settiings. We will use 'True' for the backend and 'true' for the frontend (this is not a typo, otherwise it won't work).\n\nAdd to `\u0026default-back-environment` environments\n```yml\nENABLE_GITHUB_IMPORTER: \"True\"\nGITHUB_IMPORTER_CLIENT_ID: \"client-id-from-github\"\nGITHUB_IMPORTER_CLIENT_SECRET: \"client-secret-from-github\"\n```\n\nAdd to `taiga-front` service environments\n```yml\nENABLE_GITHUB_IMPORTER: \"true\"\n```\n\n### Jira Importer\n\nActivating this feature, you will be able to import projects from Jira.\n\nFollow this documentation ([Jira - OAuth 1.0a for REST APIs](https://developer.atlassian.com/cloud/jira/platform/jira-rest-api-oauth-authentication/)) to obtain the _consumer key_ and the _public/private certificate key_.     \n\n\n\u003e **Note** \n\u003e Be careful with the upper and lower case in these settiings. We will use 'True' for the backend and 'true' for the frontend (this is not a typo, otherwise it won't work).\n\nAdd to `\u0026default-back-environment` environments\n```yml\nENABLE_JIRA_IMPORTER: \"True\"\nJIRA_IMPORTER_CONSUMER_KEY: \"consumer-key-from-jira\"\nJIRA_IMPORTER_CERT: \"cert-from-jira\"\nJIRA_IMPORTER_PUB_CERT: \"pub-cert-from-jira\"\n```\n\nAdd to `taiga-front` service environments\n```yml\nENABLE_JIRA_IMPORTER: \"true\"\n```\n\n### Trello importer\n\nActivating this feature, you will be able to import projects from Trello.\n\nFor configure Trello, you have two options:\n- go to [https://trello.com/app-key](https://trello.com/app-key) (you must login first) and obtaing your development _API key_ and your _secret key_.\n- or with the new method, [create a new Power-Up](https://developer.atlassian.com/cloud/trello/guides/rest-api/api-introduction/#managing-your-api-key) and generate an _API key_ and a _secret key_\n\n\u003e **Note** \n\u003e Be careful with the upper and lower case in these settiings. We will use 'True' for the backend and 'true' for the frontend (this is not a typo, otherwise it won't work).\n\nAdd to `\u0026default-back-environment` environments\n```yml\nENABLE_TRELLO_IMPORTER: \"True\"\nTRELLO_IMPORTER_API_KEY: \"api-key-from-trello\"\nTRELLO_IMPORTER_SECRET_KEY: \"secret-key-from-trello\"\n```\n\nAdd to `taiga-front` service environments\n```yml\nENABLE_TRELLO_IMPORTER: \"true\"\n```\n\n## Advanced configuration\n\nThe advanced configuration **will ignore** the environment variables in `docker-compose.yml` or `docker-compose-inits.yml`. Skip this section if you're using env vars.\n\nIt requires you to map the configuration files of `taiga-back` and `taiga-front` services to local files in order to unlock further configuration options.\n\n**Map a `config.py` file**\n\nFrom [taiga-back](https://github.com/taigaio/taiga-back) download the file `settings/config.py.prod.example` and rename it:\n\n```bash\nmv settings/config.py.prod.example settings/config.py\n```\n\nEdit `config.py` with your own configuration:\n\n- Taiga secret key: **it's important** to change it. It must have the same value as the secret key in `taiga-events` and `taiga-protected`\n- Taiga urls: configure where Taiga would be served using `TAIGA_URL`, `SITES` and `FORCE_SCRIPT_NAME` (see examples below)\n- Connection to PostgreSQL; check `DATABASES` section in the file\n- Connection to RabbitMQ for `taiga-events`; check \"EVENTS\" section in the file\n- Connection to RabbitMQ for `taiga-async`; check \"TAIGA ASYNC\" section in the file\n- Credentials for email; check \"EMAIL\" section in the file\n- Enable/disable anonymous telemetry; check \"TELEMETRY\" section in the file\n\nExample to configure Taiga in **subdomain**:\n```python\nTAIGA_SITES_SCHEME = \"https\"\nTAIGA_SITES_DOMAIN = \"taiga.mycompany.com\"\nFORCE_SCRIPT_NAME = \"\"\n```\n\nExample to configure Taiga in **subpath**:\n```python\nTAIGA_SITES_SCHEME = \"https\"\nTAIGA_SITES_DOMAIN = \"taiga.mycompany.com\"\nFORCE_SCRIPT_NAME = \"/taiga\"\n```\n\nCheck as well the rest of the configuration if you need to enable some advanced features.\n\nMap the file into `/taiga-back/settings/config.py`. Have in mind that you have to map it both in `docker-compose.yml` and `docker-compose-inits.yml`. You can check the `x-volumes` section in docker-compose.yml with an example.\n\n**Map a `conf.json` file**\n\nFrom [taiga-front](https://github.com/taigaio/taiga-front) download the file `dist/conf.example.json` and rename it:\n\n```bash\nmv dist/conf.example.json dist/conf.json\n```\n\nEdit it with your own configuration:\n\n- Taiga urls: configure where Taiga would be served using `api`, `eventsUrl` and `baseHref` (see examples below)\n\nExample of `conf.json` to serve Taiga in a **subdomain**:\n```json\n{\n    \"api\": \"https://taiga.mycompany.com/api/v1/\",\n    \"eventsUrl\": \"wss://taiga.mycompany.com/events\",\n    \"baseHref\": \"/\",\n```\n\nExample of `conf.json` to serve Taiga in **subpath**:\n```json\n{\n    \"api\": \"https://mycompany.com/taiga/api/v1/\",\n    \"eventsUrl\": \"wss://mycompany.com/taiga/events\",\n    \"baseHref\": \"/taiga/\",\n```\n\nCheck as well the rest of the configuration if you need to enable some advanced features.\n\nMap the file into `/taiga-front/dist/config.py`.\n\n## Configure an admin user\n\n```bash\n$ docker compose up -d\n\n$ docker compose -f docker-compose.yml -f docker-compose-inits.yml run --rm taiga-manage createsuperuser\n```\n\n## Up and running\n\nOnce everything has been installed, launch all the services and check the result:\n\n```bash\n$ docker compose up -d\n```\n\n## Configure the proxy\n\nYour host configuration needs to make a proxy to `http://localhost:9000`.\n\nIf Taiga is being served in a **subdomain**:\n```\n  server {\n      server_name taiga.mycompany.com;\n      \n      location / {\n        proxy_set_header Host $http_host;\n        proxy_set_header X-Real-IP $remote_addr;\n        proxy_set_header X-Scheme $scheme;\n        proxy_set_header X-Forwarded-Proto $scheme;\n        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n        proxy_redirect off;\n        proxy_pass http://localhost:9000/;\n      }\n      \n      # Events\n      location /events {\n        proxy_pass http://localhost:9000/events;\n        proxy_http_version 1.1;\n        proxy_set_header Upgrade $http_upgrade;\n        proxy_set_header Connection \"upgrade\";\n        proxy_set_header Host $host;\n        proxy_connect_timeout 7d;\n        proxy_send_timeout 7d;\n        proxy_read_timeout 7d;\n      }\n  \n      # TLS: Configure your TLS following the best practices inside your company\n      # Logs and other configurations\n  }\n```\n\nIf Taiga is being served in a **subpath** instead of a subdomain, the configuration should be something like:\n```\nserver {\n  server_name mycompany.com;\n  \n  location /taiga/ {\n    proxy_set_header Host $http_host;\n    proxy_set_header X-Real-IP $remote_addr;\n    proxy_set_header X-Scheme $scheme;\n    proxy_set_header X-Forwarded-Proto $scheme;\n    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n    proxy_redirect off;\n    proxy_pass http://localhost:9000/;\n  }\n  \n  # Events\n  location /taiga/events {\n    proxy_pass http://localhost:9000/events;\n    proxy_http_version 1.1;\n    proxy_set_header Upgrade $http_upgrade;\n    proxy_set_header Connection \"upgrade\";\n    proxy_set_header Host $host;\n    proxy_connect_timeout 7d;\n    proxy_send_timeout 7d;\n    proxy_read_timeout 7d;\n  }\n  \n  # TLS: Configure your TLS following the best practices inside your company\n  # Logs and other configurations\n}\n```\n\n## Change between subpath and subdomain\n\nIf you're changing Taiga configuration from default subdomain (https://taiga.mycompany.com) to subpath (http://mycompany.com/subpath) or vice versa, on top of adjusting the configuration as said above, you should consider changing the TAIGA_SECRET_KEY so the refresh works properly for the end user.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Feteriall%2Ftaiga-docker-cob","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Feteriall%2Ftaiga-docker-cob","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Feteriall%2Ftaiga-docker-cob/lists"}