Merge pull request #135 from taigaio/remove-penpot
Remove Penpot installation from taiga-docker files
This commit is contained in:
CarlosLVar
GitHub
commit
83d19c5729
39
README.md
39
README.md
|
|
@ -1,8 +1,5 @@
|
|||
# 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. |
|
||||
|---------------|:----|
|
||||
|
||||
|
|
@ -24,7 +21,7 @@ Additionally, it's necessary to have familiarity with Docker, docker compose and
|
|||
### Start the application
|
||||
|
||||
```sh
|
||||
$ ./launch-all.sh
|
||||
$ ./launch-taiga.sh
|
||||
```
|
||||
|
||||
After some instants, when the application is started you can proceed to create the superuser with the following script:
|
||||
|
|
@ -44,14 +41,6 @@ If you're testing it in your own machine, you can access the application in **ht
|
|||
|
||||
|
||||
|
||||
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:
|
||||
|
|
@ -243,7 +232,7 @@ Used for login with Github. This feature is disabled by default.
|
|||
|
||||
Follow 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.
|
||||
|
||||
> **Note**
|
||||
> **Note**
|
||||
> 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).
|
||||
|
||||
> **Note**
|
||||
|
|
@ -271,10 +260,10 @@ Used for login with GitLab. This feature is disabled by default.
|
|||
|
||||
Follow 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_.
|
||||
|
||||
> **Note**
|
||||
> **Note**
|
||||
> 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).
|
||||
|
||||
> **Note**
|
||||
> **Note**
|
||||
> `GITLAB_API_CLIENT_ID / GITLAB_CLIENT_ID` and `GITLAB_URL` should have the same value.
|
||||
|
||||
Add to `&default-back-environment` environments
|
||||
|
|
@ -298,7 +287,7 @@ PUBLIC_REGISTER_ENABLED: "true"
|
|||
|
||||
Enable Slack integration in your Taiga instance. This feature is disabled by default.
|
||||
|
||||
> **Note**
|
||||
> **Note**
|
||||
> 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).
|
||||
|
||||
Add to `&default-back-environment` environments
|
||||
|
|
@ -336,10 +325,10 @@ ENABLE_GITHUB_IMPORTER: "true"
|
|||
|
||||
Activating this feature, you will be able to import projects from Jira.
|
||||
|
||||
Follow 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_.
|
||||
Follow 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_.
|
||||
|
||||
|
||||
> **Note**
|
||||
> **Note**
|
||||
> 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).
|
||||
|
||||
Add to `&default-back-environment` environments
|
||||
|
|
@ -363,7 +352,7 @@ For configure Trello, you have two options:
|
|||
- 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_.
|
||||
- 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_
|
||||
|
||||
> **Note**
|
||||
> **Note**
|
||||
> 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).
|
||||
|
||||
Add to `&default-back-environment` environments
|
||||
|
|
@ -476,7 +465,7 @@ If Taiga is being served in a **subdomain**:
|
|||
```
|
||||
server {
|
||||
server_name taiga.mycompany.com;
|
||||
|
||||
|
||||
location / {
|
||||
proxy_set_header Host $http_host;
|
||||
proxy_set_header X-Real-IP $remote_addr;
|
||||
|
|
@ -486,7 +475,7 @@ If Taiga is being served in a **subdomain**:
|
|||
proxy_redirect off;
|
||||
proxy_pass http://localhost:9000/;
|
||||
}
|
||||
|
||||
|
||||
# Events
|
||||
location /events {
|
||||
proxy_pass http://localhost:9000/events;
|
||||
|
|
@ -498,7 +487,7 @@ If Taiga is being served in a **subdomain**:
|
|||
proxy_send_timeout 7d;
|
||||
proxy_read_timeout 7d;
|
||||
}
|
||||
|
||||
|
||||
# TLS: Configure your TLS following the best practices inside your company
|
||||
# Logs and other configurations
|
||||
}
|
||||
|
|
@ -508,7 +497,7 @@ If Taiga is being served in a **subpath** instead of a subdomain, the configurat
|
|||
```
|
||||
server {
|
||||
server_name mycompany.com;
|
||||
|
||||
|
||||
location /taiga/ {
|
||||
proxy_set_header Host $http_host;
|
||||
proxy_set_header X-Real-IP $remote_addr;
|
||||
|
|
@ -518,7 +507,7 @@ server {
|
|||
proxy_redirect off;
|
||||
proxy_pass http://localhost:9000/;
|
||||
}
|
||||
|
||||
|
||||
# Events
|
||||
location /taiga/events {
|
||||
proxy_pass http://localhost:9000/events;
|
||||
|
|
@ -530,7 +519,7 @@ server {
|
|||
proxy_send_timeout 7d;
|
||||
proxy_read_timeout 7d;
|
||||
}
|
||||
|
||||
|
||||
# TLS: Configure your TLS following the best practices inside your company
|
||||
# Logs and other configurations
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,74 +0,0 @@
|
|||
# Should be set to the public domain when penpot is going to be
|
||||
# served.
|
||||
PENPOT_FLAGS=enable-registration enable-login enable-demo-users disable-email-verification disable-smtp enable-log-emails
|
||||
PENPOT_PUBLIC_URI=http://localhost:9001
|
||||
|
||||
# Standard database connection parametes (only postgresql is
|
||||
# supported):
|
||||
PENPOT_DATABASE_URI=postgresql://penpot-postgres/penpot
|
||||
PENPOT_DATABASE_USERNAME=penpot
|
||||
PENPOT_DATABASE_PASSWORD=penpot
|
||||
|
||||
# Redis is used for the websockets notifications.
|
||||
PENPOT_REDIS_URI=redis://penpot-redis/0
|
||||
|
||||
# By default files upload by user are stored in local filesystem. But
|
||||
# it can be configured to store in AWS S3 or completelly in de the
|
||||
# database. Storing in the database makes the backups more easy but
|
||||
# will make access to media less performant.
|
||||
PENPOT_ASSETS_STORAGE_BACKEND=assets-fs
|
||||
PENPOT_STORAGE_ASSETS_FS_DIRECTORY=/opt/data/assets
|
||||
|
||||
# Telemetry. When enabled, a periodical process will send annonymous
|
||||
# data about this instance. Telemetry data will enable us to learn on
|
||||
# how the application is used based on real scenarios. If you want to
|
||||
# help us, please leave it enabled.
|
||||
PENPOT_TELEMETRY_ENABLED=true
|
||||
PENPOT_TELEMETRY_REFERER=taiga
|
||||
|
||||
# Email sending configuration. By default emails are printed in
|
||||
# console, but for production usage is recommeded to setup a real SMTP
|
||||
# provider. Emails are used for confirm user registration.
|
||||
PENPOT_SMTP_DEFAULT_FROM=no-reply@example.com
|
||||
PENPOT_SMTP_DEFAULT_REPLY_TO=no-reply@example.com
|
||||
# PENPOT_SMTP_HOST=
|
||||
# PENPOT_SMTP_PORT=
|
||||
# PENPOT_SMTP_USERNAME=
|
||||
# PENPOT_SMTP_PASSWORD=
|
||||
# PENPOT_SMTP_TLS=true
|
||||
# PENPOT_SMTP_SSL=false
|
||||
|
||||
## Authentication providers
|
||||
|
||||
# Google
|
||||
# PENPOT_GOOGLE_CLIENT_ID=
|
||||
# PENPOT_GOOGLE_CLIENT_SECRET=
|
||||
|
||||
# Github
|
||||
# PENPOT_GITHUB_CLIENT_ID=
|
||||
# PENPOT_GITHUB_CLIENT_SECRET=
|
||||
|
||||
# Gitlab
|
||||
# PENPOT_GITLAB_BASE_URI=https://gitlab.com
|
||||
# PENPOT_GITLAB_CLIENT_ID=
|
||||
# PENPOT_GITLAB_CLIENT_SECRET=
|
||||
|
||||
# OpenID Connect (since 1.5.0)
|
||||
# PENPOT_OIDC_BASE_URI=
|
||||
# PENPOT_OIDC_CLIENT_ID=
|
||||
# PENPOT_OIDC_CLIENT_SECRET=
|
||||
|
||||
# LDAP
|
||||
# PENPOT_LDAP_HOST=ldap
|
||||
# PENPOT_LDAP_PORT=10389
|
||||
# PENPOT_LDAP_SSL=false
|
||||
# PENPOT_LDAP_STARTTLS=false
|
||||
# PENPOT_LDAP_BASE_DN=ou=people,dc=planetexpress,dc=com
|
||||
# PENPOT_LDAP_BIND_DN=cn=admin,dc=planetexpress,dc=com
|
||||
# PENPOT_LDAP_BIND_PASSWORD=GoodNewsEveryone
|
||||
# PENPOT_LDAP_ATTRS_USERNAME=uid
|
||||
# PENPOT_LDAP_ATTRS_EMAIL=mail
|
||||
# PENPOT_LDAP_ATTRS_FULLNAME=cn
|
||||
# PENPOT_LDAP_ATTRS_PHOTO=jpegPhoto
|
||||
# PENPOT_LOGIN_WITH_LDAP=true
|
||||
|
||||
|
|
@ -1,83 +0,0 @@
|
|||
---
|
||||
############################################################
|
||||
# NOTE: All the configuration is located in the
|
||||
# `docker-compose.penpot.env` file.
|
||||
############################################################
|
||||
|
||||
version: "3.5"
|
||||
|
||||
networks:
|
||||
penpot:
|
||||
|
||||
volumes:
|
||||
penpot_postgres_data:
|
||||
penpot_assets_data:
|
||||
|
||||
services:
|
||||
penpot-frontend:
|
||||
image: "penpotapp/frontend:latest"
|
||||
ports:
|
||||
- 9001:80
|
||||
|
||||
volumes:
|
||||
- penpot_assets_data:/opt/data
|
||||
|
||||
env_file:
|
||||
- docker-compose.penpot.env
|
||||
|
||||
depends_on:
|
||||
- penpot-backend
|
||||
- penpot-exporter
|
||||
|
||||
networks:
|
||||
- penpot
|
||||
|
||||
penpot-backend:
|
||||
image: "penpotapp/backend:latest"
|
||||
volumes:
|
||||
- penpot_assets_data:/opt/data
|
||||
|
||||
depends_on:
|
||||
- penpot-postgres
|
||||
- penpot-redis
|
||||
|
||||
env_file:
|
||||
- docker-compose.penpot.env
|
||||
|
||||
networks:
|
||||
- penpot
|
||||
|
||||
penpot-exporter:
|
||||
image: "penpotapp/exporter:latest"
|
||||
env_file:
|
||||
- docker-compose.penpot.env
|
||||
|
||||
environment:
|
||||
# Don't touch it; this uses internal docker network to
|
||||
# communicate with the frontend.
|
||||
- PENPOT_PUBLIC_URI=http://penpot-frontend
|
||||
networks:
|
||||
- penpot
|
||||
|
||||
penpot-postgres:
|
||||
image: "postgres:13"
|
||||
restart: always
|
||||
stop_signal: SIGINT
|
||||
|
||||
environment:
|
||||
- POSTGRES_INITDB_ARGS=--data-checksums
|
||||
- POSTGRES_DB=penpot
|
||||
- POSTGRES_USER=penpot
|
||||
- POSTGRES_PASSWORD=penpot
|
||||
|
||||
volumes:
|
||||
- penpot_postgres_data:/var/lib/postgresql/data
|
||||
|
||||
networks:
|
||||
- penpot
|
||||
|
||||
penpot-redis:
|
||||
image: redis:6
|
||||
restart: always
|
||||
networks:
|
||||
- penpot
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
#!/usr/bin/env sh
|
||||
|
||||
# This Source Code Form is subject to the terms of the Mozilla Public
|
||||
# License, v. 2.0. If a copy of the MPL was not distributed with this
|
||||
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
|
||||
#
|
||||
# Copyright (c) 2021-present Kaleidos INC
|
||||
|
||||
set -x
|
||||
exec docker compose -f docker-compose.yml -f docker-compose.penpot.yml up -d $@
|
||||
Loading…
Reference in New Issue