Inconsistent use of absolute_url vs. relative_url filter

[vorth]

I'm using a Docker container to test my site, either locally or with a GitHub Codespace. It works marvelously, for everything except one detail: many of the links are absolute URLs saying "http://0.0.0.0:4000/...". These are constructed as href attributes something like this:

href="{{ post.url | absolute_url }}"

These will never work in a container environment, since the container and server cannot possibly know how traffic is being directed to them, often through some generated domain name.

The relative_url filter seems to be the appropriate one in all cases, as far as I can tell. Your theme has about an even mix of both absolute_url and relative_url. Is there a reason they are not all relative_url?

[ReenigneArcher]

I also test in docker and have it working fine, but had to add a second config.

• Dockerfile: https://github.com/LizardByte/LizardByte.github.io/blob/master/Dockerfile
• docker config: https://github.com/LizardByte/LizardByte.github.io/blob/master/_config_local.yml

May not be the best solution, but it does work.

[daattali]

Also related #1431

[vorth]

@daattali it would be great if you could answer my question... why not always relative_url?