How is TracWikiPrintPlugin supposed to work in a container?

[Martin]

Dears,

I'm not sure, how I need to configure TracWikiPrintPlugin to work in my
environment.

I have a container with Trac 1.6, which can be accessed on the container
over HTTP (without TLS) on port 8081, i.e. http://localhost:8081/

There is a frontend nginx which does HTTPS on port 443, let's say
https://trac.myserver.example/

I see, that TracWikiPrintPlugin calls wkhtmltopdf with the "public"
domain and port, https://trac.myserver.example/ instead of the
"internal" one, http://localhost:8081/

I can configure the container in way, that it can access the frontend
nginx (at the moment, it can't), but I'm not sure, if it would be better
if wkhtmltopdf would use http://localhost:8081/ — but how would I
configure that in TracWikiPrintPlugin?

Thanks in advance!

Cheers, Martin

[Markus Rosjat]

Hi Martin,

I don't really know the plugin but as far as my experience with trac goes, without any tinkering in the code trac will always try to get the system working with the project url you provide in the config.

So if you cant do some settings for the plugin in the trac.ini or Admin Pages you will be stuck with the  "public" url.

Cheers markus 

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/875y356oo3.fsf%40fama.lan.

[Martin]

Hi Markus,

On 2023-10-17 21:34, Markus Rosjat wrote:
> I don't really know the plugin but as far as my experience with trac goes, without any tinkering in the code trac will always try to get the system
> working with the project url you provide in the config.
> So if you cant do some settings for the plugin in the trac.ini or Admin Pages you will be stuck with the "public" url.

Thanks, I will use the public URL then.

Cheers