Alexander Block

@rawlingsj What do the docker/docker-compose logs say?

@rawlingsj Did you follow the instructions on https://github.com/htdvisser/taiga-docker/tree/stable/taiga-back? My first guess would be that you did not do the "Database Initialization" part. If you did that, then I don't know...

@rawlingsj so is everything working? if yes, I think this one can be closed?

@rawlingsj You should check the backend logs as well in this case. If it does not show anything, try to figure out if there is anything to enable verbose debug...

@juliusvonkohout Sorry about that, I definitely plan to revive this topic in the future but from a different perspective.

fyi, this was my naive approach to add `noindex` to one of my pages. I'm not that experienced with Hugo, so I might have missed the "correct" way to do...

I started to analyse the underlying issue that causes slowdowns in the project I'm working and figured out that this issue is the underlying issue. I also delved into go-git...

@pjbgf Thanks. Yeah that's what I assumed already. And I was not aware of #825, which will clearly also fix the underlying performance issue, but without the incompatible API change....

I can confirm that this is a bug and supposed to work, so the docs are correct, but the implementation is wrong. The `get_var` and `render` function is currently only...

This issue seems to be more complicated then I thought. It's a combination of missing functionality in Jinja2 and bugs in go-jinja2. See this PR, which tries to fix it...