by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    QP Hou
    @houqp
    @joedissmeyer It's a custom hmac based auth protocol, so you can't use standard http auth. Here is a sample client that uses the custom auth method with requests: https://github.com/houqp/iris-python-client/blob/master/src/irisclient/__init__.py#L18.
    Yuvaraj L
    @skyrocknroll
    Hello Team , I have raised an pull request linkedin/iris#470 for smtp auth support. Can somebody review and merge ?
    @houqp Can you help here ?
    Daniel Wang
    @dwang159
    LGTM
    Sheepdog
    @CamHopkin_twitter
    Hi all I have been working on trying to get IRIS up and running using virtual env and https://medium.com/@angellom/deploying-linkedins-iris-to-aws-as-a-docker-image-cba6b1cf14cf on aws but I keep hitting walls
    is there just like a docker container that I can throw up and be done with it?
    Sheepdog
    @CamHopkin_twitter
    well that second one looks really really easy
    Sheepdog
    @CamHopkin_twitter
    that iris-docker-compose would be great but I think iris-api is not there anymore
    Sheepdog
    @CamHopkin_twitter
    Ok tried both of those the first one puts me in the same spot I am now where its looking for the mysql db
    docker run quay.io/iris/iris Checking MySQL liveness on 127.0.0.1... DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. DB not up yet. Waiting a few seconds.. Waited too long for DB to come up. Bailing.
    Sorry not sure hot to format that nicer
    Sheepdog
    @CamHopkin_twitter
    so Trying https://quay.io/repository/iris/iris?tab=info nets me the same error about waiting for the db as above. Same with the medium link for deploying in AWS. in aws I can confirm that mysql is up and running - do I have to throw open a port?
    Daniel Wang
    @dwang159
    iirc Iris expects to be able t o talk to mysql on localhost:3306
    check the config to make sure DB credentials are correct?
    Sheepdog
    @CamHopkin_twitter
    So where do I change that because we have tried a few spots
    when I setup the db it's a default one and I can log in using root and generic pw that I made
    we have tried all forms of variation on
    'sudo docker run -e DOCKER_DB_BOOTSTRAP=1 \
    -e IRIS_CFG_DB_USER=root -e IRIS_CFG_DB_PASSWORD=1234 -e IRIS_CFG_DB_HOST=localhost \
    quay.io/iris/iris:latest'
    and I have verified that mysql is running
    Daniel Wang
    @dwang159
    and the DB is running on the same host as Iris?
    Sheepdog
    @CamHopkin_twitter
    yes
    all 1 instance
    Daniel Wang
    @dwang159
    hmm, let me take a look at the docker-compose
    what was the issue with that one?
    Sheepdog
    @CamHopkin_twitter
    iris api doesn't exist as a repo
    I think was it
    it's looking for relay and api and api is removed

    Cloning into 'iris-api'...
    git@github.com: Permission denied (publickey).
    fatal: Could not read from remote repository.

    Please make sure you have the correct access rights
    and the repository exists.
    make: * [serve] Error 128

    Daniel Wang
    @dwang159
    oh, try replacing that with linkedin/iris
    I think we renamed the repo at some point
    Sheepdog
    @CamHopkin_twitter
    tried to rename in the make file still not a go
    look like compose probably needs an update to remove stuff from iris-api and iris_api dependencies
    do we need to do any port forwarding from the container to the instance?
    Daniel Wang
    @dwang159
    ok, tinkered around with docker-compose and made some changes: jrgp/iris-docker-compose#5
    linking mysql properly in docker is a huge pain
    Sheepdog
    @CamHopkin_twitter
    Yes that is the issue I was having lol
    Sheepdog
    @CamHopkin_twitter
    @dwang159 this is looking a lot more promising - thank you for your help! First time in days I have an Iris Login Screen :)
    Sheepdog
    @CamHopkin_twitter
    Does there happen to be an oncall-docker-compose lurking around that is similar to the docker one?
    QP Hou
    @houqp
    i am not aware of any, but it should be a lot easier to setup since it just one service (unlike iris), you can find examples in https://github.com/linkedin/oncall/tree/master/ops/packer
    Sheepdog
    @CamHopkin_twitter
    It is easier however I am getting errors on will see if I can dig into the logs but oncall just throwing an internal error status
    Sheepdog
    @CamHopkin_twitter
    Something is wrong in the code for this container
    Sheepdog
    @CamHopkin_twitter
    http://localhost:8080/ goes to an error: Internal Server Error
    I think it has something to do with something in the container itself - I checked and can see nginx
    Sheepdog
    @CamHopkin_twitter
    I threw up issue #244 for my problems running this
    Sheepdog
    @CamHopkin_twitter
    Found logs showing there is an issue updated my issue with the log
    MagicBrownson
    @MagicBrownson
    Howdy Iris Team! Is there a plan about moving Iris and other repos around Iris to Python 3 soon?
    MagicBrownson
    @MagicBrownson
    Perhaps there is a fork in the repo I did not see yet...
    Ah,,, I see the branch now.