项目管理看板系统Taiga源代码涵盖Docker部署项目

# Taiga Docker | :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). | |---------------|:----| | :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. | |---------------|:----| > **Note:** > 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) ## Getting Started This section intends to explain how to get Taiga up and running in a simple two steps, using **docker** and **docker compose**. If you don't have docker installed, please follow installation instructions from [docker.com](https://docs.docker.com/engine/install/) (**version 19.03.0+**) Additionally, it's necessary to have familiarity with Docker, docker compose and Docker repositories. > **Note** > branch `stable` should be used to deploy Taiga in production and `main` branch for development purposes. ### Start the application ```sh $ ./launch-all.sh ``` After some instants, when the application is started you can proceed to create the superuser with the following script: ```sh $ ./taiga-manage.sh createsuperuser ``` The `taiga-manage.sh` script lets launch manage.py commands on the back instance: ```sh $ ./taiga-manage.sh [COMMAND] ``` If 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.  As **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** It'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.  And finally if you just want to launch Taiga standalone, you can use the `launch-taiga.sh` script instead of the `launch-all.sh`. ## Documentation Currently, we have authored three main documentation hubs: - **[API](https://docs.taiga.io/api.html)**: Our API documentation and reference for developing from Taiga API. - **[Documentation](https://docs.taiga.io/)**: If you need to install Taiga on your own server, this is the place to find some guides. - **[Taiga Community](https://community.taiga.io/)**: This page is intended to be the support reference page for the users. ## Bug reports If you **find a bug** in Taiga you can always report it: - in [Taiga issues](https://tree.taiga.io/project/taiga/issues). **This is the preferred way** - in [Github issues](https://github.com/kaleidos-ventures/taiga-docker/issues) - send us a mail to support@taiga.io if is a bug related to [tree.taiga.io](https://tree.taiga.io) - send us a mail to security@taiga.io if is a **security bug** One of our fellow Taiga developers will search, find and hunt it as soon as possible. Please, 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. ## Community If 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/). If 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. ## Contribute to Taiga There 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). ## Code of Conduct Help us keep the Taiga Community open and inclusive. Please read and follow our [Code of Conduct](https://github.com/kaleidos-ventures/code-of-conduct/blob/main/CODE_OF_CONDUCT.md). ## License Every 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. Please read carefully [our license](LICENSE) and ask us if you have any questions as well as the [Contribution policy](https://github.com/kaleidos-ventures/taiga-docker/blob/main/CONTRIBUTING.md). ## Configuration We'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. Both `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**. Refer to these sections for further information. ## Basic Configuration You will find basic **configuration variables** in the `.env` file. As stated before, we encourage you to edit these values, especially those affecting the security. ### Database settings These vars are used to create the database for Taiga and connect to it. ```bash POSTGRES_USER=taiga # user to connect to PostgreSQL POSTGRES_PASSWORD=taiga # database user's password ``` ### URLs settings These vars set where your Taiga instance should be served, and the security protocols to use in the communication layer. ```bash TAIGA_SCHEME=http # serve Taiga using "http" or "https" (secured) connection TAIGA_DOMAIN=localhost:9000 # Taiga's base URL SUBPATH="" # it'll be appended to the TAIGA_DOMAIN (use either "" or a "/subpath") WEBSOCKETS_SCHEME=ws # events connection protocol (use either "ws" or "wss") ``` The default configuration assumes Taiga is being served in a **subdomain**. For example: ```bash TAIGA_SCHEME=https TAIGA_DOMAIN=taiga.mycompany.com SUBPATH="" WEBSOCKETS_SCHEME=wss ``` If Taiga is being served in a **subpath**, instead of a subdomain, the configuration should be something like this: ```bash TAIGA_SCHEME=https TAIGA_DOMAIN=mycompany.com SUBPATH="/taiga" WEBSOCKETS_SCHEME=wss ``` ### Secret Key settings This variable allows you to set the secret key in Taiga, used in the cryptographic signing. ```bash SECRET_KEY="taiga-secret-key" # Please, change it to an unpredictable value! ``` ### Email Settings By 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: ```bash EMAIL_BACKEND=console # use an SMTP server or display the emails in the console (either "smtp" or "console") EMAIL_HOST=smtp.host.example.com # SMTP server address EMAIL_PORT=587 # default SMTP port EMAIL_HOST_USER=user # user to connect the SMTP server EMAIL_HOST_PASSWORD=password # SMTP user's password EMAIL_DEFAULT_FROM=changeme@example.com # email address for the automated emails # EMAIL_USE_TLS/EMAIL_USE_SSL are mutually exclusive (only set one of those to True) EMAIL_USE_TLS=True # use TLS (secure) connection w