victoria wrote: > Hi, > > Confirmed. The new link for windows should work also on Windows > 64bits. > >
Yep, the second installer worked. It's a bit unusual to end up with 32-bits software installed below C:\Program Files, though (should be "C:\Program Files (x86)" on Windows x64 systems). However, I made the mistake to use a project name containing spaces - the environment path is correctly quoted, but not the projectname argument after initenv: Error running C:\Program Files\BitNami Trac Stack/python/python.exe "C:\Program Files\BitNami Trac Stack\trac\Scripts\trac-admin-script.py" "C:\Users\cboos\BITNAM~1\BitNami Trac 0.11.6" initenv BitNami Trac 0.11.6 sqlite:db/trac.db svn "C:\Users\cboos\BitNami Trac Stack repository" Then, trying to fix that by using the "Use BitNami Trac stack" cmd shell, I saw that trac-admin was not available. The "C:\Program Files\BitNami Trac Stack\trac\Scripts" path should be put in the PATH, for that shell (in the ./scripts/setenv.bat file). After fixing it: >trac-admin "C:\Users\cboos\BitNami Trac Stack projects\BitNami Trac 0.11.6" initenv "BitNami Trac 0.11.6" sqlite:db/trac.db svn "C:\Users\cboos\BitNami Trac Stack repository" Creating and Initializing Project ... Congratulations! At that point, the environment was reachable via tracd: >tracd "C:\Users\cboos\BitNami Trac Stack projects\BitNami Trac 0.11.6" -p 9999 But not via Apache, I had to restart first, no big deal. Authentication was correctly set up, though for a more effective start, one would expect that the user specified in the installer would end up having the TRAC_ADMIN permissions, so that you can start right away configuring your environment. The README.txt file still talks about the WebAdmin plugin as an example - bad example, as you should *not* install the 0.10.x WebAdmin plugin in Trac 0.11.x, which has the admin panels built in. A part from those minor glitches (which I think are easy to fix), it works great, mod_python is correctly configured. In addition, it would be great if HTTP access to the svn repository would be configured as well, so that people could start commit code to their project right away ;-) I also like the very clean way everything is organized below "C:\Program Files\BitNami Trac Stack", but apparently it's in part theoretical, as the actual install of python Lib and DLLs is duplicated below apache2/bin. If one wants to upgrade Trac manually (hint for fellow Trac developers, try out 0.12dev!), then the .eggs, .pths and all that have to end up *there*). Hope you'll find the advice helpful. On my side, I'll use the BitNami Trac as a nice test environment for mod_python 3.3.1 on Windows ;-) -- Christian PS: hint for other Trac developers: if you want to "upgrade" such a BitNami install to 0.12dev, then use the provided python to perform the installation, as admin (btw. I'd be interested to know how to get a separate trac012\Lib\site-pages folder, instead of installing in python\Lib\site-packages), then be sure to modify/delete ./apache2/bin/Lib/site-packages/trac.pth -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
