Suggestion: Single container setup

[Supersnellehenk]

Hi,

I've been trying for the past couple of weeks to get Taiga 6 running on unRAID, which using Portainer and it's docker compose function didn't really work. I've also tried setting it up in a VM (Ubuntu), got it almost working but I keep getting CORS errors to the API.

My major complaint is the overcomplicated docker compose setup, especially when trying to set it up in something like unRAID, which is more designed around single containers and templates.

So, I'd like to simplify the setup greatly, by putting a working Taiga setup in a SINGLE container and just map some config files that I can edit. This way the setup is easier, because everything works out of the box. 

I've been slamming my head against my desk for a while now. I'd love to use Taiga, but the setup is just too complicated for me.

[Gyorgy Marton]

Hi, I got some CORS errors it was caused by configuration in ~/taiga-front/dist/conf.json Check what value have set in "api"  

I forked taiga-scripts a while back give it a try in a fresh 20.04 VM https://github.com/dev633a/taiga-script it is what I use to quickly (~10 mins) install.

[quen...@electropositive.co.nz]

I agree with Supersnellehenk, the docker setup is unnecessarily complicated.  For the Enterprise market that would actually use so many differing dockers because of some requirement for a massively scaled Taiga implementation might be 1% of the customer market on here if they're lucky. For the rest of us, docker is meant to simplify and reduce possibility of misconfiguration.  In this case docker is as hard if not harder than a VM, a situation I've never before seen with docker.

All we need is front/back/events in a single container, and the option to have an external database really.  Thats my wish list.

After a sort of extreme amount of effort for a docker container, I did get the docker running, but alas events don't run and I'm worried that if I did get it running, something else will go wrong which I would have to rely on community support to fix.  This would all be solved by a simplified single docker image.

It's a shame that such an obviously great product is hamstrung by it's implementation.

[Yamila Moreno]

Hi there!

About the mention that the docker setup is "unnecessarily complicated"; could you give more detail? which complications did you find? With the "30 minute setup" (https://resources.taiga.io/30min-setup/) you can have a Taiga working quite easily. In fact, you can run it out of the box (although it's not recommended to keep the default credentials). Recently we simplify the docker-compose to make it more accesible, but we are open to suggestions to make it more clear.

All we need is front/back/events in a single container, and the option to have an external database really.  Thats my wish list.

This is a fair list, but it doesn't have all the services that are needed to have the complete experience of Taiga. The core services for Taiga are:

- back - for the API

- async - for the async tasks

- events - for the real time events

- protected - to manage tokens for attachments

- postgresql - as a database

- rabbitmq - to async and events

- front - typically with a static files server (nginx was our choose)

 

After a sort of extreme amount of effort for a docker container, I did get the docker running, but alas events don't run and I'm worried that if I did get it running, something else will go wrong which I would have to rely on community support to fix.  This would all be solved by a simplified single docker image.

About the single container, we're following the good practices of docker, where a container should have only one service to keep isolation. We're well aware that there are other valid approaches, but currently we're sticking to this one. That said, I refer to what I mentioned above about improving the docker-compose.

Besides, all the dockerfiles are public in their respective repositories, and you could create your own image with all the services, and I strongly recommend that if you follow this path, have in mind all the services mentioned, not only the 3 in your wishlist, so you can have a complete Taiga.

 

My major complaint is the overcomplicated docker compose setup, especially when trying to set it up in something like unRAID, which is more designed around single containers and templates.

The official images are public so anyone can use them and the taiga-docker repository is a working example about how to make it work with docker-compose. And of course, we plan to improve and extend the distribution of Taiga in the future.

Cheers!

--

	Yamila Moreno Suárez COO & Cofounder   kaleidos.net

Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su destinatario, y pudiendo contener información confidencial sometida a secreto profesional, o cuya divulgación esté legalmente prohibida. Cualquier opinión en él contenida es exclusiva de su autor y no representa necesariamente la opinión de la empresa. Si ha recibido este mensaje por error, le rogamos nos lo comunique de forma inmediata por esta misma vía y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. El correo electrónico vía Internet no es seguro y no se puede garantizar que no haya errores ya que puede ser interceptado, modificado, perdido o destruido, o contener virus. Cualquier persona que se ponga en contacto con nosotros por correo electrónico se considerará que asume estos riesgos. KALEIDOS OPEN SOURCE se reserva las acciones legales que le correspondan contra todo tercero que acceda de forma ilegítima al contenido de cualquier mensaje externo procedente del mismo. INFORMACIÓN PROTECCIÓN DE DATOS. Responsable: KALEIDOS OPEN SOURCE (B86241973) Le informamos que sus datos identificativos y los contenidos en los correos electrónicos y ficheros adjuntos pueden ser incorporados a nuestras bases de datos con la finalidad de mantener relaciones profesionales y/o comerciales y, que serán conservados mientras se mantenga la relación. Si lo desea, puede ejercer su derecho a acceder, rectificar y suprimir sus datos y demás reconocidos normativamente dirigiéndose al correo emisor o en los datos del responsable. Para información y consultas visite nuestra web  https://kaleidos.net