I have no idea what that is like at all. Seriously. ;-)
How I wish I could be the same!!
Actually, I was being sarcastic. I don't think I even get to go a whole
day on just one job.
Right now, its about 3-4 ppl who'll be working on the server, of which only
1-2 might work simultaneously. So, from what you're saying I guess its not
necessary to have a MySQL DB.
I would agree.
But since the Snow Leopard server comes with
MySQL pre-installed, we'll probably move to that when we install trac on the
server.
That's what I would do.
In the meantime, I'll try and get another trac project running with
MySQL(after the installation procedure as you've explained in the mail) on
my system. I hope this is possible - to run a trac project on sqlite while
the other runs on mysql (both standalone).
As long as they have different .ini files and point at different
databases, that's fine. You can even do two different ones on MySQL or
two on SQLite, as long as the actual databases (the MySQL DB name or the
SQLite table) are not the same.
This would ease my paranoia of being able to set it up with MySQL on the
server later on.
Understandable.
Is the Trac website the best place to direct new users to, to get a basic
idea of how it works?
We wrote up a basic "GettingStartedWithTrac" page and linked to it from
the main Wiki page. This allowed us to craft a help page which is
optimized for what most people do here, addresses our workflow and
procedures, and explains several plugins which are installed. Of course,
this varies by installation, so custom help is kind of the only way that
it works.
--
Matthew Caron
Build Engineer
Sixnet | www.sixnet.com
O +1 518 877 5173 Ext. 138
F +1 518 602 9209
[email protected]
--
You received this message because you are subscribed to the Google Groups "Trac
Users" 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-users?hl=en.
