Alternative container

[blackandred]

Hi, I also created a container, maybe you would like to connect efforts?

Features:

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

The project is at:
https://github.com/riotkit-org/docker-taiga

[w1ck3dg0ph3r]

Hi! Thanks for letting me know! I definitely would like to merge efforts on this, as I have not enough spare time nor experience with TravisCI to automate building images.

This said, I'm unsure as of now about putting all the things in the single container. Mainly because this eliminates ability to independently scale different components for large scale setup.

Let me look deeper into your pipeline when I have a chance and come back to you on this to elaborate on how to handle this best.

[christianlupus]

I just wanted to open a new issue with this content:

Would you accept a PR regarding CI updating and building the docker files once new taiga releases are brought up? I'd look into this if you like but I do not want to put effort into it if you do not want to do something in this direction.

As I found this issue, I wanted to ask what the progress is. Further, I'd just ask if it would be better to go with travis or with GitHub actions. In another project I recently was working with travis they were hitting some github api rate limits...

[blackandred]

Hi, I designed the CI to build containers once a month for Taiga, the project is stable and slowly maintained.
I didn't notice the issue with github api rate limits, but if there will be any issue - I will add authorization.