Ilias Lazaridis kirjoitti:
I've understood that upgrading of minor versions is non-critical:
Actually upgrades between minor versions are generally good thing to do
and it doesn't involve usually upgrade of trac environment (that's those
database files etc. you manage with trac-admin)
Between major versions you might need to upgrade trac environment and
maybe delete and completely install new version of Trac software.
http://projects.edgewall.com/trac/wiki/TracUpgrade#From0.9.3to0.9.4
but important:
http://projects.edgewall.com/trac/wiki/ChangeLog#a0.9.5
-
I am a bit unclear about how to proceed:
How do I upgrade trac with a minimum or no downtime?
You don't need downtime, it you usually can do it on the fly, except:
1) You're running fastcgi or mod_python and running something other on
same webserver (you need restart webserver)
2) You're running on filesystem/backup software that doesn't lock files
while backing them up and you absolutely want to back things up.
Is there any standard procedure available for this?
Backup environment, (stop server,) (remove old version,) install new,
upgrade environment if needed (,start server), test.
But in my experience (I've been using and upgrading Trac since 0.8xx) I
have upgraded always on the fly (running in CGI mode) only thing I had
sometimes to do was to upgrade all trac environments with simple script.
This is possibly more a python oriented question:
Can I install 2 versions of trac, thus I can fall-back if the upgrade
fails for any reason?
No because differences in project environment mainly database part (well
in theory this could be possible, but to have two non-related
environments and keeping them in-sync would be a real challenge)
--
Jani Tiainen
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
