I’m interested to install taiga for a small team (<20 members) and not an intensive usage.
Self hosting is interesting to integrate taiga in internal service with SSO.
Is it possible to integrated taiga with oidc (keycloak, working really). Is there a way to have a light weight installation without deploying 8 containers over 2 docker-compose.
thanks
I am working with an org that is similar in size to yours, and are self-hosting Taiga with the 2 docker-compose file approach. We have been running it since the start of this year.
The server is a t3.medium AWS instance, currently using about 1.5 of 4GB RAM. Here’s a snapshot of docker stats that you might find interesting
I keep logs of all CPU load throughout the day, Monday it didn’t jump above 0.65 during peak time. The 5 minute average was generally about 0.10. This is with two vCPUs.
We also are running OIDC. Not with keycloak but with another self-hosted OIDC (we are hosting Ory Hydra as the OIDC OP, on separate infrastructure). I had to make some tweaks to this OIDC plugin to support our needs (such as locking down which users can login) but it works well enough. You can see the 3 PRs there are from me.
There are other OIDC plugins too,GitHub - robrotheram/taiga-contrib-openid-auth: Taiga plugin for openid authentication (but I didn’t like the way that one doesn’t set a state/nonce etc, I’m not convinced it’s safe enough to use as an OIDC RP). Some people have filed issues in that one about problems with Keycloak too. Search for ‘Keycloak’ on this forum, I think quite a few people are using it.
I’d be happy to help you if you run into any issues with setting it up. The usual OIDC pain points are not unique to Taiga but typical to any RP, e.g making sure you set the correct post-login redirect URI callback correctly, etc.