[Trac] Trac basics

[James Mohr]

Hi All! I am writing an article on ticketing systems and have come across some issues that I would like to address in the article. As far as I can see, there is no way to create users or define permissions through the GUI. I looked at the TracPermissions page, and it seems that the only way to manage users, groups and permissions is with the trac-admin tool. Is that correct? Is there no way (yet) of doing it through the GUI? Please tell me if I say anything that it incorrect. The TracInstall page says "(either SQLite, PostgreSQL, or MySQL works)". After downloading http://ftp.edgewall.com/pub/trac/trac-0.10.tar.gz, I looked in the INSTALL file and it says: Trac is written in the Python programming language and can use SQLite or PostgreSQL as database. What about MySQL? Looking in the RELEASE file, I find "Trac now features experimental support for the MySQL database." There is obviously some contradictory documenation, but after a bit of work and digging through several different docs, I get passed this point. When I try to set it up with trac-admin /data/home/public_html/trac initenv I have the prompt: Database connection string [sqlite:db/trac.db]> This would seem to indicate that it defaults to SQLite. I assumed that I could change this, so I tried "mysql:tracuser/tracdb". This does not generate an error at this point but waits until the installation seems be be complete, and reports: Failed to create environment. Database connection string mysql:tracuser/tracdb must start with scheme:/ After digging through the doc, I found what I believe to be the appropriate syntax, but I cannot re-run the initenv because I get the message "Does an environment already exist?" The only way to correct this is to manually remove the contect of the directory specified. Wouldn't it have been more logical to first check that everything is defined as expected *before* making changes to the system? I found out when I first tried to access the system that ClearSilver was not installed, nor did the DB table get created. These are things that can be checked during the initialization, but obviously were not. You have to input the mysql connect string, but other than writing it to a a file it isn't used, but should be to test that the values are correct. Wouldn't it have been more logical to include links from the TracInstall page to DatabaseBackend rather than to the home page of the respective database? Naturally, there is really no limited and one could create as many links as necessary. However, I would think that a person reading an installation doc would be more intersting in knowing *how* to use one of the other DBs as opposed to learning "what* these other DBs are. I must admit that not having good documentation is one of my pet peaves, especially when the installation does not do proper checking and you reach a point where you have to correct things by hand. This is compounded by the problem that "Trac Installation Guide" lists only a fraction of the necessary steps and it seems that unless everything is installed *exactly* as Trac expects it even before your start, then the install fails with various messages. Best Regards, Jim Mohr --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~----------~----~----~----~------~----~------~--~---