Question: If I build the container using the following compose file there seems to be no official Taiga documentation for adding my own `contribPlugins` to taiga-frontend. #7

Leopere · 2019-08-25T17:00:12Z

version: '3.7'

services:
  taiga:
#    image: quay.io/riotkit/taiga:4.2.7
    build:
      context: ./docker-taiga/
      #dockerfile: .
      args:
        - TAIGA_BACK_VERSION=4.2.13
        - TAIGA_FRONT_VERSION=4.2.13-stable
    networks:
      - traefik
      - default
    volumes:
      - ./media:/usr/src/taiga-back/media
    environment:
      TAIGA_SECRET_KEY: secret
      TAIGA_HOSTNAME: taiga.REDACTED
      TAIGA_SCHEME: https
      TAIGA_DB_NAME: taiga
      TAIGA_DB_USER: taiga
      TAIGA_DB_HOST: postgres
      TAIGA_DB_PASSWORD: dbpassword
      TAIGA_ENABLE_EMAIL: 'True'
      TAIGA_EMAIL_FROM: REDACTED
      TAIGA_EMAIL_USE_TLS: 'True'
      TAIGA_EMAIL_HOST: REDACTED
      TAIGA_EMAIL_PORT: 465
      TAIGA_EMAIL_USER: REDACTED
      TAIGA_EMAIL_PASS: REDACTED
    #deploy:
    labels:
      - "traefik.backend=taiga"
      - "traefik.docker.network=traefik"
      - "traefik.frontend.rule=Host:taiga.REDACTED"
      - "traefik.enable=true"
      - "traefik.port=80"

  postgres:
    image: postgres
    environment:
      POSTGRES_DB: taiga
      POSTGRES_USER: taiga
      POSTGRES_PASSWORD: dbpassword
    volumes:
      - ./postgres:/var/lib/postgresql/data
      
volumes:
  postgres:
  media:
    
networks:
  traefik:
    external: true

Any ideas as to how to get contribPlugins working?

zicklag · 2019-08-25T17:04:04Z

We'll have to add support to for adding a list of contribPlugins to the conf.json file to this container. That would be a simple change. The bigger problem is deciding how to allow users of the container to add plugins. What plugin are you wanting to install? ( So I can look at the installation instructions )

Leopere · 2019-08-25T17:48:11Z

Realistically I’d love to have Trello and github importers but it’s very unclear thanks to sparse Taiga documentation how to do that.

…

On Sun, Aug 25, 2019 at 1:04 PM Zicklag ***@***.***> wrote: We'll have to add support to for adding a list of contribPlugins to the conf.json file to this container. That would be a simple change. The bigger problem is deciding how to allow users of the container to add plugins. What plugin are you wanting to install? ( So I can look at the installation instructions ) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AAIE2VQ45ODCI6T6VXNLKJLQGK3QJA5CNFSM4IPJT2LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CXNSI#issuecomment-524646089>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIE2VTB6MMJZTY5H3GVXDDQGK3QJANCNFSM4IPJT2LA> .

zicklag · 2019-08-25T17:59:31Z

Oh, that's super easy. Those importers are actually built-in and just have to be enabled in the config file. We can add environment variables that allow you to enable/disable those importers.

Leopere · 2019-08-25T18:20:37Z

That would be great! I was just going to build it but if you support it in the mainline I’m even more happy.

…

On Sun, Aug 25, 2019 at 1:59 PM Zicklag ***@***.***> wrote: Oh, that's super easy. Those importers are actually built-in and just have to be enabled in the config file. We can add environment variables that allow you to enable/disable those importers. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AAIE2VRYJD74YQUYDZ5JDVDQGLCAHA5CNFSM4IPJT2LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CYSAQ#issuecomment-524650754>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIE2VR75N7655SRR6QYCCTQGLCAHANCNFSM4IPJT2LA> .

Leopere · 2019-08-25T19:57:29Z

This comment seems to relate to #3 so just mentioning it in this feed for the sake of consistency.

blackandred · 2019-08-26T09:03:24Z

Could you propose anything @zicklag, I mean some code/PR? I didn't dive into this topic yet.

zicklag · 2019-08-26T16:37:09Z

I should be able to open a PR soon.

Leopere · 2019-08-26T19:19:02Z

This is all I could find pointing to contribPlugins in their official documentation for Taiga.io

Leopere · 2019-08-26T19:20:46Z

Oh, and one other detail, if we're going to have this assert a bunch of things into how Taiga runs we should define an order of precedence so that if someone has modified the configuration in various ways like a volume'd config or something of the sort we should respect that by default.

zicklag · 2019-08-26T21:33:38Z

Right now, all of the Taiga settings ( at least the Taiga back settings ) that are set by the container are in a docker-settings.py file that is included into the local.py settings file. If you wanted to replace the local.py file with your own file in a Docker volume, then all of the settings in there would take precedence over the ones set in the docker-settings.py file.

Also, most, if not all, of the settings set in docker-settings.py are configuable through environment variables, so if you want to change them, you can change them without having to mount a config file or rebuild the container.

When I create the PR for enabling the other importers I'll have them on by default and provide environment variables that allows you to chose which ones to disable/enable.

Leopere · 2019-09-02T20:06:05Z

This sounds like the kind of behavior that I would hope to expect. I'm kind of miffed that out of all of the best practices that Docker people write they don't discuss the order of precedence when it comes to designing an ideal Dockerfile.

blackandred · 2019-09-29T06:24:48Z

Any news on this? 😉

I got a request on the Slack plugin in the Taiga image, I don't know if you have already some progress? 🙂

zicklag · 2019-09-29T16:01:55Z

No, I haven't done anything for it. :)

If I remember right, the best idea was just to have something like a pugins.d directory that all of the shell scripts put in that directory would be run by the entrypoint at startup. That would mean that you could do whatever kind of setup was necessary to install whatever plugins you wanted.

I don't think Taiga plugins are standardized enough to have a universal plugin install method.

blackandred · 2019-09-29T16:51:42Z

Hmm... One thing I'm sure - we need to install plugins at build stage - installing plugins on entrypoint is very, very bad practice that cannot run on serious production systems. So the solution would be to install them first, then toggle enable on entrypoint (using environment variables).

…

On Sun, Sep 29, 2019 at 6:01 PM Zicklag ***@***.***> wrote: No, I haven't done anything for it. :) If I remember right, the best idea was just to have something like a pugins.d directory that all of the shell scripts put in that directory would be run by the entrypoint at startup. That would mean that you could do whatever kind of setup was necessary to install whatever plugins you wanted. I don't think Taiga plugins are standardized enough to have a universal plugin install method. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AFOAJBWXNPZ45BRTEE5FIEDQMDGPHA5CNFSM4IPJT2LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD73YOXY#issuecomment-536315743>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFOAJBWQYSKMBVRIQXUEVB3QMDGPHANCNFSM4IPJT2LA> .

zicklag · 2019-09-29T21:11:17Z

I agree with that. I wasn't sure if you wanted to be able to install arbitrary plugins at runtime or not, but I would definitely opt for creating derivative images if you need custom plugins.

Otherwise, integrating more commonly useful plugins such as LDAP seems like a good idea if somebody has the need for it and doesn't mind contributing.

It wasn't hard for me to add LDAP support. I pretty much just followed the installation instructions and added the environment configuration scripts.

blackandred · 2019-09-30T04:34:49Z

I don't think there are a lot of contrib plugins. We can do an infrastructure for plugins, then on request (when issue will be created) add plugins with acceptance (unstable plugins should not be accepted, as we will have difficulties to maintain the image, and deletion of a non-building plugin later could be a breaking change).

blackandred · 2019-09-30T04:35:10Z

Ah, and at first we can just add Slack with such method.

blackandred · 2019-10-02T06:11:39Z

@zicklag Could I assign you to this?

zicklag · 2019-10-02T18:13:44Z

I'm not sure when I would be able to get to it. I've been a bit busy, but if you wanted to assign it to me I could do it if I do find the time.

Leopere · 2019-10-02T18:42:15Z

Mark it for #hacktoberfest and they can get the shirt.

…

On Wed, Oct 2, 2019 at 2:11 AM Andrew Johnson ***@***.***> wrote: @zicklag <https://github.com/zicklag> Could I assign you to this? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AAIE2VUVFBNXUNCTNSJYGZ3QMQ3RZA5CNFSM4IPJT2LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEADVLMQ#issuecomment-537351602>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIE2VTLCR7PKDOEHITYGZDQMQ3RZANCNFSM4IPJT2LA> .

blackandred · 2019-10-02T20:27:58Z

We can be assigned both, haha. So we will see who will start it 😄

Leopere · 2019-10-02T21:29:30Z

The main plugin I would love is taiga's trello sync plugin. If we get any more then that's excellent. I don't think this feature add has to be extensive just check if someone has changed a variable from it's default TAIGA_PLUGIN=${TAIGA_PLUGIN:-FALSE} if it doesn't switch from FALSE to TRUE then don't bother adding the plugin. Then you could build the APP on container init. Unless of course that would be super slow.

zicklag · 2019-10-02T21:40:13Z

The Trello importer is actually already merged. It came with #12.

Leopere · 2019-10-02T21:42:09Z

Shows how often I'm updating my in-dev containers. I have a constant sprawl of web-apps that I'm testing in my docker-compose micro services cluster. Taiga is one of the ones that've been in my list of todo for ages.

unixfox · 2019-11-11T11:38:44Z

I would love to see the slack plugin added :).

blackandred · 2019-11-11T13:09:45Z

I would love to see the slack plugin added :).

ACK :)
Will try to find a time this week to implement it, and by the way improve the versioning.

Leopere · 2019-11-11T13:59:52Z

Just for the sake of taking care of anyone who searches up how to do this in the future can we have a proper docker-compose.yml example posted in this thread. Even modifying my example I posted to open the thread.

Sceat · 2019-11-12T16:23:19Z

subbed! really need the slack contrib :)

blackandred · 2019-11-20T05:46:24Z

I'm working on it.

blackandred · 2019-11-26T06:29:24Z

Sorry, that it is taking so long, I had to take care about my backup servers at first, then get back to this project.

I'm on the way, will be testing this possibly tommorow.

blackandred · 2019-11-27T07:33:13Z

I almost implemented it. The frontend currently does not install properly, it's just a lack of my time - I need to spend an one hour next day to have it finished and tested. I guess, that's my estimation.

The plugin system will install everything at build time, and let the devops decide on container startup which plugins to enable.

Leopere · 2019-11-27T17:41:28Z

Makes sense honestly the inclusion of the plugins probably doesn't really increase the build size that much and if they're really concerned about the containers being that small they should likely be using a different solution. Taiga really doesn't seem lightweight on usage.

blackandred · 2019-11-29T06:07:12Z

Ok, I'm testing it. I released a first RC. If something would be wrong I would release another RC, when it will be stable I will tag a normal version 1.0 of the container

https://github.com/riotkit-org/docker-taiga/releases/tag/1.0-RC1

blackandred · 2019-11-29T06:07:46Z

If everything will be ok, then the RC should be on quay as an RC version.

blackandred · 2019-11-29T06:14:27Z

Damn, actually the CI is blocked because Taiga.io released backend v5.0.0 and frontend v5.0.1 and they didn't release frontend v5.0.0. Assumption that frontend version == backend version seems to be wrong. I will have figure out some solution that would pick next closest release.

blackandred · 2019-11-29T07:49:33Z

It seems that locally I got it working. Trying to make the CI working.

I created an additional ticket:
#23

blackandred · 2019-12-27T12:05:19Z

Hi! Please check new builds on Quay, the plugins support is there. Also all versions are building now. The #23 was resolved.

Closing now. Please open a new issue in case that something would not work. Thanks 🙂

blackandred · 2019-12-27T22:13:59Z

I invite you to check the recent stable release - 1.0 of the image - quay.io/riotkit/taiga:5.0.2-b1.0, https://github.com/riotkit-org/docker-taiga/releases

blackandred added the FEATURE New feature or request label Oct 2, 2019

blackandred assigned blackandred and zicklag Oct 2, 2019

blackandred added a commit that referenced this issue Nov 27, 2019

#7: Pre-implement plugins

25349aa

blackandred added a commit that referenced this issue Nov 28, 2019

#7: Implement migration/setup on onetrypoint for plugins

f7d16dc

blackandred added a commit that referenced this issue Nov 29, 2019

#7: Updated docs

408fd08

blackandred mentioned this issue Nov 29, 2019

Build a closest frontend release that would match backend version #23

Closed

blackandred closed this as completed Dec 27, 2019

Question: If I build the container using the following compose file there seems to be no official Taiga documentation for adding my own contribPlugins to taiga-frontend. #7

Question: If I build the container using the following compose file there seems to be no official Taiga documentation for adding my own contribPlugins to taiga-frontend. #7

Comments

Leopere commented Aug 25, 2019

zicklag commented Aug 25, 2019

Leopere commented Aug 25, 2019 via email

zicklag commented Aug 25, 2019

Leopere commented Aug 25, 2019 via email

Leopere commented Aug 25, 2019

blackandred commented Aug 26, 2019

zicklag commented Aug 26, 2019

Leopere commented Aug 26, 2019

Leopere commented Aug 26, 2019 • edited Loading

zicklag commented Aug 26, 2019

Leopere commented Sep 2, 2019

blackandred commented Sep 29, 2019 • edited Loading

zicklag commented Sep 29, 2019

blackandred commented Sep 29, 2019 via email

zicklag commented Sep 29, 2019 • edited Loading

blackandred commented Sep 30, 2019

blackandred commented Sep 30, 2019

blackandred commented Oct 2, 2019

zicklag commented Oct 2, 2019

Leopere commented Oct 2, 2019 via email

blackandred commented Oct 2, 2019

Leopere commented Oct 2, 2019

zicklag commented Oct 2, 2019 • edited Loading

Leopere commented Oct 2, 2019

unixfox commented Nov 11, 2019

blackandred commented Nov 11, 2019

Leopere commented Nov 11, 2019

Sceat commented Nov 12, 2019

blackandred commented Nov 20, 2019

blackandred commented Nov 26, 2019

blackandred commented Nov 27, 2019

Leopere commented Nov 27, 2019

blackandred commented Nov 29, 2019

blackandred commented Nov 29, 2019

blackandred commented Nov 29, 2019

blackandred commented Nov 29, 2019

blackandred commented Dec 27, 2019

blackandred commented Dec 27, 2019

Question: If I build the container using the following compose file there seems to be no official Taiga documentation for adding my own `contribPlugins` to taiga-frontend. #7

Question: If I build the container using the following compose file there seems to be no official Taiga documentation for adding my own `contribPlugins` to taiga-frontend. #7

Leopere commented Aug 26, 2019 •

edited

Loading

blackandred commented Sep 29, 2019 •

edited

Loading

zicklag commented Sep 29, 2019 •

edited

Loading

zicklag commented Oct 2, 2019 •

edited

Loading