How to get links for [Taiga USs, Tasks and Issues references] working with HTTPS?

[myii...@gmail.com]

We've got Taiga working locally with HTTPS and all is going well so far.  Just to be clear, the HTTPS unwrapping is done by the load balancer (Pound in our case) and Taiga hasn't been configured for HTTPS at all (default Nginx configuration).

However one issue I have is with the links produced by [Taiga USs, Tasks and Issues references].  Examples:
In local.py:

SITES["front"]["domain"] = "https://[our domain]"

Give link references:

http://https//[our domain]/project/[project-name]/task/5

Instead of:

https://[our domain]/project/[project-name]/task/5

Yet if local.py contains just the domain name:

SITES["front"]["domain"] = "[our domain]"

Then we still get only http:

http://[our domain]/project/[project-name]/task/5

I've seen that the examples shown at https://taiga.io/support/taiga-markdown-syntax/#taiga-uss-tasks-and-issues-references all link to https://... so obviously it can be done.

Just in case it is important, main.json for taiga-front contains:

"api": "/api/v1/"

I haven't checked just yet but I'm expecting that the e-mail messages generated will suffer from the same problem.

Thanks for any help you can offer.

[David Barragán]

Try with

SITES["front"]["scheme"] = "https"

SITES["front"]["domain"] = "[our domain]"

Regards

---

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

--
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/0f92ec2b-32bf-4fa5-bdc0-10b254a9485e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[myii...@gmail.com]

Excellent, that worked.  Thanks for that - and your promptness is exemplary - fantastic.

The only issue I had was that I tried all of the following but it still didn't work:

$ sudo service circus restart
$ circusctl restart
$ circusctl reload

I had to `vagrant reload` before it worked.  To be honest, I've always wondered which of the above to use, since I've seen all three of them mentioned in the documentation, yet none of them worked in this case!

1. Is there any idea why it didn't work until the complete reload?
2. In any case, which of the three is best to use?  Or are there situations where you need to use each one?

Otherwise, thanks again for the help.

[Alejandro Alonso]

Hello,

 

$ sudo service circus restart

This one restart the the circus server

 

$ circusctl restart

This one restart the circus services (taiga, taiga-events...)

 

$ circusctl reload

This one reloads the circus services (taiga, taiga-events...). Reload doesn't stop and start the service (like restart does).

For that kind of changes a reload would be the better way (it doesn't stop the server so your users won't have any milliseconds down) 

Regards,

--

Alejandro Alonso Fernández   CIO & Co-founder alejandr...@kaleidos.net  | Tel: (+34) 627263808 | (+34) 913562995 www.kaleidos.net/FC8EAC/

[myii...@gmail.com]

Thanks for clearing that up.  Good to see that the docs are going to be updated with this solution as well - saves me putting in a pull request!  Good job all round!