Sign inSign up

mferraroni/docker-taiga-front

By mferraroni

•Updated over 9 years ago

Frontend for taiga project management tool

Image
0

999

mferraroni/docker-taiga-front repository overview

Travis Docker Pulls ImageLayer Beevelop

beevelop/taiga-front

⁠beevelop/taiga-front

Taiga⁠ is a project management platform for startups and agile developers & designers who want a simple, beautiful tool that makes work truly enjoyable.

This Docker image allows you to run the Taiga frontend. It works together with the beevelop/taiga-back⁠ image.

⁠Running

A beevelop/taiga-back⁠ needs to be linked as taigaback. Also connect the volumes of the taiga-back container if you want to serve the static files for the admin panel.

docker run --name taiga_front -p 8080:80 --link taiga_back_container:taigaback --volumes-from taiga_back_container beevelop/taiga-front

You should then be a able to access the Taiga-Frontend at http://YOUR_HOST:8080 and login with the username admin and the password 123123.

⁠Docker-Compose⁠

⁠Environment

  • PUBLIC_REGISTER_ENABLED: defaults to the respective Taiga-Back configuration or true
  • FEEDBACK_ENABLED: defaults to the respective Taiga-Back configuration or true
  • GITHUB_API_CLIENT_ID: provide a GitHub API ID to enable GitHub OAuth
  • DEFAULT_LANGUAGE: defaults to en
  • DEFAULT_THEME: defaults to taiga (also available (as of Taiga's source code), but untested: material-design, high-contrast)
    • Feedback on these settings is appreciated

⁠Sign-Up / Register

Users will have to accepts those terms in order to register. Therefore these settings are only relevant if PUBLIC_REGISTER_ENABLED is true.

  • PRIVACY_POLICY_URL: provide an URL to your own privacy policy (default null)
  • TERMS_OF_SERVICE_URL: provide an URL to your own TOS (default null)

⁠API and SSL

  • API defaults to "/api/v1"
  • SCHEME defaults to http. If https is used either
    • SSL_CRT and SSL_KEY needs to be set or
    • /etc/nginx/ssl/ volume attached with ssl.crt and ssl.key files
  • SSL_CRT SSL certificate value. Valid only when SCHEME set to https.
  • SSL_KEY SSL certificate key. Valid only when SCHEME set to https.

HTTPS can be enabled by setting SCHEME to https and filling SSL_CRT and SSL_KEY env variables (see Environment section below). http (port 80) requests will be redirected to https (port 443).

⁠Debugging

  • DEBUG_ENTRYPOINT: set to True to enable Debugging (set -x)
  • DEBUG defaults to false

⁠Credit

This image was originally adapted from htdvisser/taiga-front-dist.

Tag summary

Content type

Image

Digest

Size

45.8 MB

Last updated

over 9 years ago

docker pull mferraroni/docker-taiga-front