On Saturday, January 2, 2021 at 6:11:21 PM UTC-8 rcp....@gmail.com wrote:
> Thanks Ryan, > > I'd checked trac.wsgi initially as that was my first thought. However, it > was actually pointing at the correct Python in the first line so I made the > silly mistake of assuming that Deploy had NOT overwritten my trac.wsgi. As > it happens it had, blowing away my customisations further down the script > to work around the bug in passenger - wsgi as well as other changes > obviously necessary to get Trac to work in a Virtual Environment in my > Centos 7 + WHM + cPanel setup. > > Regarding the deploy command replacing customised wsgi scripts (and > presumably the other trac.*gi scripts in the cgi-bin directory) how much > effort would be involved in comparing the new scripts with existing ones > and alerting the user if there is a change? To partly answer my own > question, I hunted through the Trac code and found the relevant code here > <https://trac.edgewall.org/browser/trunk/trac/env.py#L993>. As someone > with only a very superficial understanding of how Trac works and with a > limited knowledge of Python I'd have thought it wouldn't be too difficult > to tweak the code to manage the situation where there is a change to one of > these two scripts. > > If you think it's worth considering, I'm happy to add a ticket describing > a proposed workflow and perhaps even have a go at submitting a patch. > I would like to do something to address this situation, but it would seem to be more straightforward to either add a switch to the deploy command for "htdocs only", or add a "redeploy" command that extracts htdocs but doesn't touch cgi-bin. Ryan -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/28385fed-2920-435a-91f8-0797a4943ed1n%40googlegroups.com.
