Dead project - reactivation

[blackandred]

Hi, I see this project looks dead. I forked it and set up a fully automated container build.

Features:

• Production-ready setup (using gunicorn instead of python's built-in development server)
• Stable versioning (tagged Taiga releases + dated snapshots. Dated snapshots are immutable, as main tags can be updated in case of a hotfix)
• Automatic building of each new Taiga release on Travis CI (using for-each-github-release toolkit from RiotKit CI Utils)
• Automatic documentation in README.md generated from parsed ENV variables and comments placed in Dockerfile

Please take a look at:
https://github.com/riotkit-org/docker-taiga

[LaysDragon]

for latest version there is another folk is already latest and can work with original helm of this repo
https://github.com/mvitale1989/docker-taiga
https://github.com/mvitale1989/helm-taiga

[LaysDragon]

taiga with the latest version requirement of python is upgrade to version 3
I feel it will not easy to update from 4.2.12 to 4.2.14
especially for those contributed modules plugin and some docker and helm deployment

[LaysDragon]

I don't known the reason,but I notice there is some of taiga related repo is stop active.
some contributed modules repo and this docker&helm repo.

[blackandred]

Python 2 as far as I know will be not maintained anymore soon, so that's a mandatory change.
Why the repositories are outdated? I don't know - that's one of reasons why I set up the CI to build new versions of Taiga automatically.

[nikto-b]

Looks like this project is rly dead
Postgres configuration is already invalid and an app API returns HTTP500 for login because "django.db.utils.ProgrammingError"
Maybe archieving will be best solution

[benhutchins]

I agree. I'll archive this repo.

[blackandred]

There are official Taiga images now.