taiga-vagrant redirects to localhost

[alba...@gmail.com]

Hi there!

I attended your talk on Taiga last week at DevOps Madrid and I'm already using it for a project! It seems much more useful and appealing to my team than our standard Redmine system.

One thing that I found weird is that once Taiga is deployed through taiga-vagrant, some URL redirections are consistently thrown to localhost. I found this taking place when uploading an avatar image for an user or when adding a new wiki page. In both cases the link to the resource points to the localhost URL, regardless of whether the actual Taiga installation is indeed on localhost or some server. This results in broken links and an unusable wiki when taiga-vagrant is deployed in a remote server.

I suppose the fix to this ought to be as simple as editing some config file, but I have no clue where to start looking. Any suggestions?

Regards,
Álvaro.

[David Barragán]

Hi Álvaro,

you have to edit taiga-back/settings/local.py

SITES = {
    "api": {
        "scheme": "http",
        "domain": "localhost:8000",
        "name": "api"

    },

    "front": {

       "scheme": "http",

       "domain": "localhost:9001",

       "name": "front"

    },

}

Then you only have to restart taiga-back with

circusctrl restart taiga

Thank you very much for your words and for using Taiga.

Best regards

--
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/3f89b7d6-ca83-439d-aa67-226e6322f42b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---

David Barragán Merino   Engineer david.b...@kaleidos.net  | Tel: (+34) 913562995 www.kaleidos.net/FFF8E7

[Álvaro Barbero Jiménez]

Thanks for your answer David!

I actually had to modify the config a little bit, and write:

SITES = {
    "api": {
            "scheme": "http",

            "domain": "MYSERVER:8000",

            "name": "api"
    },
    "front": {
            "scheme": "http",

            "domain": "MYSERVER:8000",
            "name": "front"
    },
}

using port 9001 for the front would not work for linked wiki pages. With these changes everything seems to run smoothly now!

Regards,
Álvaro.

[nikos.al...@unepgrid.ch]

Can you provide a concrete example of what does not work with port 9001?  And why?

Thank you, Nikos

[Álvaro Barbero Jiménez]

Sorry for the very late reply.

Essentially, what would happen is that some of the linked resources would get pointed by incorrect URLs. I observed this:

• Uploading a user defined avatar image. The image would get uploaded succesfully, but every link to the image would point to a wrong URL.
• Creating a wiki page. When the new page is linked from the wiki entry, that link would point to the wrong place.

I didn't delve enough to understand why this happens, but changing the ports as prompted above solved the issue.

Regards,

Álvaro.