trac-admin should upgrade static files in environment

[anatoly techtonik <techtonik@…>]

Trac 0.11 doesn't upgrade static files in environment. Therefore bugfixes in JS code and CSS styles are not propagated into environment. trac-admin upgrade should try to update them (if it knows where these static files are - and ideally it should know this even if these files are fetched only through web-server directly). If Trac can not update these resources automatically - it should at least instruct users how to update manually, i.e. use trac-admin deploy and compare to detect what files are modified. If Trac has embedded differ, it may try to do this automatically. At the very least it should propose to read wiki TracUpgrade page for more information.

P.S. Plugin installation/upgrade instructions should also include trac-admin deploy step to refresh resources.

[Carsten Klein <carsten.klein@…>]

How about adding a redeploy action similar to upgrade that will first run upgrade and then redeploy any static files found in the plugins' and trac's distribution archives?

E.g.

> trac-admin . redeploy
Upgrading environment....done.
Deploying static files...done.

[anatoly techtonik <techtonik@…>]

I don't think this deserves a separate command. There is already a plenty of them.

$ PYTHON_EGG_CACHE=.egg-cache trac-admin . deploy delme2
Command failed: Destination already exists. Specify --update to proceed.

$ PYTHON_EGG_CACHE=.egg-cache trac-admin . deploy --update delme2
The following files have changed/added and will be updated:
M delme2/cgi-bin/trac.wsgi
M delme2/htdocs/common/css/browser.css
M delme2/htdocs/common/css/diff.css
M delme2/htdocs/common/js/blame.js
M delme2/htdocs/common/js/expand_dir.js
M delme2/htdocs/common/js/trac.js
A delme2/htdocs/dozer/excanvas.compiled.js
A delme2/htdocs/dozer/jspark.js
A delme2/htdocs/dozer/main.css
Show (d)iff or continue [yn]?

[Christian Boos]

deploy certainly deserves some well-thought improvements, but definitely not for 0.11.7.1, and even for 0.12 it's a bit late.

[anatoly techtonik <techtonik@…>]

Replying to cboos:

deploy certainly deserves some well-thought improvements, but definitely not for 0.11.7.1, and even for 0.12 it's a bit late.

The problem with all release cycles that people lose motivation to contribute, because they are not able to use the results of their contributions in production environments. That's why all active "development" is only active around release dates.

[Thijs Triemstra <lists@…>]

Replying to anatoly techtonik <techtonik@…>:

The problem with all release cycles that people lose motivation to contribute, because they are not able to use the results of their contributions in production environments. That's why all active "development" is only active around release dates.

0.13 perhaps?

[Remy Blank]

Replying to Thijs Triemstra <lists@…>:

0.13 perhaps?

Only when we get a good patch. Until then, we'd rather leave it in next-major.

Please have a look at our milestone descriptions, especially the "notes to maintainers". This should give you an idea of how we use our milestones. Feel free to suggest improvements to the descriptions if you think they aren't clear enough.

[Ryan J Ollos]

The deploy command extracts the scripts in cgi-bin. This is a convenience when installing Trac, but the default scripts rarely change and sometimes the user customizes their cgi script. It would be useful to have an option to extract static resources without modifying the cgi scripts. See ​gmessage:trac-users:y2RNJvg7mwQ/wAdEVDD7BwAJ.