Re: [Trac] Trac on OSX

[David Chase]

I don't know if this is helpful, but I "run" three different Trac servers, one 
on a Solaris box, and two on Mac boxes.  For the two Macs, I used MacPorts to 
install (and keep up to date) the software.  This has worked quite well for me.

One advantage of using an sqlite(3) database is that you can usually do a live 
backup of an entire site just using rsync; one of the Mac-Tracs is a backup of 
the Solaris site, running on my laptop.  Because they are running different 
Trac versions, I have to upgrade the database after each backup (and make minor 
modifications to trac.ini).

Understand, on the Mac, I faked out the Solaris file system so that the server 
"sees" the same directory structure, but the server includes a tricky rendering 
plugin that caches images, and otherwise invokes emacs in batch mode, then 
pdflatex, then an image-mutating program, all from a Python script.  And 
MacPorts keeps it all up to date, and it works identically on the two servers 
(to the best of my ability to tell).

So, I very much recommend using MacPorts, and just going with what is the 
canned install, especially if you are just a few people.

David Chase

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

Re: [Trac] Trac on OSX

[Matthew Caron]

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
matt.ca...@sixnet.com

--
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

Re: [Trac] Trac on OSX

[cap_sue]

Wow!! You're great help...where do I click to give 5-star rating??

>I have no idea what that is like at all. Seriously. ;-)

How I wish I could be the same!!

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. But since the Snow Leopard server comes with
MySQL pre-installed, we'll probably move to that when we install trac on the
server.

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).

This would ease my paranoia of being able to set it up with MySQL on the
server later on.

Is the Trac website the best place to direct new users to, to get a basic
idea of how it works?


Matthew Caron-2 wrote:
> 
> On 11/11/2010 04:14 AM, cap_sue wrote:
>> Thanks a lot for your input and sorry that I have taken so long to
>> respond.
>> I was working on other stuff and only got back to the Trac installation
>> now.
> 
> I have no idea what that is like at all. Seriously. ;-)
> 
> (No worries)
> 
>> I have successfully managed to create authentication and once logged in,
>> I
>> can see the New Ticket field.
> 
> Excellent.
> 
>> I have another (or a few) question(s).
> 
> Ask away.
> 
>> Would it be possible to continue using sqlite for actual bugtracking
>> purposes or will i run out of database space soon and/or are the feature
>> in
>> sqlite very limited compared to MySQL? In other wods, what would be the
>> advantage of going with MySQL as opposed to sqlite.
> 
> MySQL is a real database server. It has a finer granularity of locking, 
> better concurrency, less latency, etc.
> 
> SQLite is a database engine, suitable for small installations and 
> embedding into applications. It is easier to set up, as you don't have 
> to set up a daemon, tweak much of anything, worry that much about 
> security, etc.
> 
> You won't really run into space issues with either, until you run out of 
> disk space. You also won't (generally) run into compatibility/feature 
> issues as Trac is programmed to be reasonably database abstract. 
> However, you might run into problems with plugins which call direct SQL 
> commands rather than the Trac API, as they may not have been programmed 
> as conservatively as core Trac is. This is generally not a big deal - 
> fix the SQL until it works, file a bug with the plugin maintainer, 
> submit a patch, get on with life.
> 
> That said, you will likely run into scalability issues. If you're 
> supporting two users, and don't intend in going over about five people 
> in the near future, then don't worry about it - just use SQLite. Once 
> you hit about 5-10 heavy users, however, you'll start seeing issues with 
> people stepping on each other (you'll start seeing "database is locked" 
> timeout errors) and then you'll need to migrate to a real DB server.
> 
> Also note that any custom reports you do will be all on you. I've 
> specifically run into variances with time-related ones, as MySQL, 
> PostgreSQL and SQLite all have different date-handling functions. Also, 
> the quoting can be subtly different (PostgreSQL wants single quotes).
> 
>> We do have a SnowLeopard Server which I can use to install trac once I
>> establish trac is working fine on my system. In that case, I do have
>> MySQL
>> pre-installed on the Server OS. Would there be a big difference in the
>> procedure to set up the trac project if I went for a MySQL DB?
> 
> Depends on how paranoid you are and how much functionality you need.
> 
> With SQLite, you just point the ini file at the file you want to use 
> and, once it is created, restrict permissions so someone else can't fire 
> up the SQLite CLI client and modify it, while not breaking the 
> permissions necessary for trac to work. Generally, the correct owner and 
> permissions 0644 do the trick, which also means your nightly stats 
> gathering scripts can dump the db to, say, email each manager a summary 
> of the day's events.
> 
> With MySQL, you (or, at least I)
>   - Install it
>   - Create root user
>   - Create empty trac db
>   - Create trac user with access only to that db
>   - Point trac.ini at that DB with those credentials
>   - Since trac.ini now has credentials, lock it down so no one can read 
> it except those who need to
>   - Create a readonly user with SELECT permissions (so that nightly 
> scripts can query the DB, as mentioned above)
> 
> It's is not particularly difficult, just a little bit more work.
> -- 
> Matthew Caron
> Build Engineer
> Sixnet | www.sixnet.com
> O +1 518 877 5173 Ext. 138
> F +1 518 602 9209
> matt.ca...@sixnet.com
> 
> -- 
> You received this message because you are subscribed to the Google Groups
> "Trac Users" group.
> To post to this group, send email to trac-us...@googlegroups.com.
> To

Re: [Trac] Trac on OSX

[Matthew Caron]

On 11/11/2010 04:14 AM, cap_sue wrote:

Thanks a lot for your input and sorry that I have taken so long to respond.
I was working on other stuff and only got back to the Trac installation now.


I have no idea what that is like at all. Seriously. ;-)

(No worries)


I have successfully managed to create authentication and once logged in, I
can see the New Ticket field.


Excellent.


I have another (or a few) question(s).


Ask away.


Would it be possible to continue using sqlite for actual bugtracking
purposes or will i run out of database space soon and/or are the feature in
sqlite very limited compared to MySQL? In other wods, what would be the
advantage of going with MySQL as opposed to sqlite.


MySQL is a real database server. It has a finer granularity of locking, 
better concurrency, less latency, etc.


SQLite is a database engine, suitable for small installations and 
embedding into applications. It is easier to set up, as you don't have 
to set up a daemon, tweak much of anything, worry that much about 
security, etc.


You won't really run into space issues with either, until you run out of 
disk space. You also won't (generally) run into compatibility/feature 
issues as Trac is programmed to be reasonably database abstract. 
However, you might run into problems with plugins which call direct SQL 
commands rather than the Trac API, as they may not have been programmed 
as conservatively as core Trac is. This is generally not a big deal - 
fix the SQL until it works, file a bug with the plugin maintainer, 
submit a patch, get on with life.


That said, you will likely run into scalability issues. If you're 
supporting two users, and don't intend in going over about five people 
in the near future, then don't worry about it - just use SQLite. Once 
you hit about 5-10 heavy users, however, you'll start seeing issues with 
people stepping on each other (you'll start seeing "database is locked" 
timeout errors) and then you'll need to migrate to a real DB server.


Also note that any custom reports you do will be all on you. I've 
specifically run into variances with time-related ones, as MySQL, 
PostgreSQL and SQLite all have different date-handling functions. Also, 
the quoting can be subtly different (PostgreSQL wants single quotes).



We do have a SnowLeopard Server which I can use to install trac once I
establish trac is working fine on my system. In that case, I do have MySQL
pre-installed on the Server OS. Would there be a big difference in the
procedure to set up the trac project if I went for a MySQL DB?


Depends on how paranoid you are and how much functionality you need.

With SQLite, you just point the ini file at the file you want to use 
and, once it is created, restrict permissions so someone else can't fire 
up the SQLite CLI client and modify it, while not breaking the 
permissions necessary for trac to work. Generally, the correct owner and 
permissions 0644 do the trick, which also means your nightly stats 
gathering scripts can dump the db to, say, email each manager a summary 
of the day's events.


With MySQL, you (or, at least I)
 - Install it
 - Create root user
 - Create empty trac db
 - Create trac user with access only to that db
 - Point trac.ini at that DB with those credentials
 - Since trac.ini now has credentials, lock it down so no one can read 
it except those who need to
 - Create a readonly user with SELECT permissions (so that nightly 
scripts can query the DB, as mentioned above)


It's is not particularly difficult, just a little bit more work.
--
Matthew Caron
Build Engineer
Sixnet | www.sixnet.com
O +1 518 877 5173 Ext. 138
F +1 518 602 9209
matt.ca...@sixnet.com

--
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

Re: [Trac] Trac on OSX

[cap_sue]

Hi Matthew,

Thanks a lot for your input and sorry that I have taken so long to respond.
I was working on other stuff and only got back to the Trac installation now.

I have successfully managed to create authentication and once logged in, I
can see the New Ticket field.

I have another (or a few) question(s).

Right now, I have installed trac on my machine (which isn't the server) just
to see how the installation goes and since sqlite was already a part of my
OS (Snow Leopard) I didn't install MySQL. 

Would it be possible to continue using sqlite for actual bugtracking
purposes or will i run out of database space soon and/or are the feature in
sqlite very limited compared to MySQL? In other wods, what would be the
advantage of going with MySQL as opposed to sqlite.

We do have a SnowLeopard Server which I can use to install trac once I
establish trac is working fine on my system. In that case, I do have MySQL
pre-installed on the Server OS. Would there be a big difference in the
procedure to set up the trac project if I went for a MySQL DB?



Matthew Caron-2 wrote:
> 
> On 10/22/2010 04:47 AM, cap_sue wrote:
>> http://trac.edgewall.org/wiki/TracInstall, I've managed to get trac
>> running
>> on the standalone server, tracd. However, I don't see the "New Ticket"
>> tab
>> on the right side of the page.
> 
> Depending on how you have it configured, you may need to log in first.
> 
> 
>> Also, I'm not sure how/where to add the
>> information under configuring authentication. Can somebody please help?
> 
> According to the docs, it looks like you tell it where the password file 
> is. See here:
> 
> http://trac.edgewall.org/wiki/TracStandalone#UsingAuthentication
> 
> It appears that the password file is htpasswd/htdigest, which you can 
> generate with apache tools.
> 
> Where are you getting stuck on these steps?
> -- 
> Matthew Caron
> Build Engineer
> Sixnet | www.sixnet.com
> O +1 518 877 5173 Ext. 138
> F +1 518 602 9209
> matt.ca...@sixnet.com
> 
> -- 
> You received this message because you are subscribed to the Google Groups
> "Trac Users" group.
> To post to this group, send email to trac-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> trac-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/trac-users?hl=en.
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Trac-on-OSX-tp30026741p30188334.html
Sent from the Trac Users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

Re: [Trac] Trac on OSX

[Matthew Caron]

On 10/22/2010 04:47 AM, cap_sue wrote:

http://trac.edgewall.org/wiki/TracInstall, I've managed to get trac running
on the standalone server, tracd. However, I don't see the "New Ticket" tab
on the right side of the page.


Depending on how you have it configured, you may need to log in first.



Also, I'm not sure how/where to add the
information under configuring authentication. Can somebody please help?


According to the docs, it looks like you tell it where the password file 
is. See here:


http://trac.edgewall.org/wiki/TracStandalone#UsingAuthentication

It appears that the password file is htpasswd/htdigest, which you can 
generate with apache tools.


Where are you getting stuck on these steps?
--
Matthew Caron
Build Engineer
Sixnet | www.sixnet.com
O +1 518 877 5173 Ext. 138
F +1 518 602 9209
matt.ca...@sixnet.com

--
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

[Trac] Trac on OSX

[cap_sue]

Hello all,

I'm installing trac on osx(Snow Leopard - 10.6.4). After running through the
steps listed on the TracGuide page -
http://trac.edgewall.org/wiki/TracInstall, I've managed to get trac running
on the standalone server, tracd. However, I don't see the "New Ticket" tab
on the right side of the page. Also, I'm not sure how/where to add the
information under configuring authentication. Can somebody please help?

My setup is as below:

MAC OS X - 10.6.4
Python - 2.6 (comes with osx)
setuptools - 0.6c11 (come with os x)
Genshi - 0.6 (installed using easy_install)

sqlite - 3.6.12 (comes with osx)

I'm still trying to configure apache so that it can be deployed over it. If
somebody can guide me through those steps as well, I'd be very grateful.
This is the first time, I'm even dealing with sql/python/webservers and so
am quite lost!! :( Any tips would be appreciated.

Thank you!
-- 
View this message in context: 
http://old.nabble.com/Trac-on-OSX-tp30026741p30026741.html
Sent from the Trac Users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

[Trac] Trac on Osx Server

[Cesare Montresor]

Hi,
I'm having some troble to install trac on osx server 10.6 (minimac).
I tried to follow this guide  but
seams out of date and many paths are incorrect or missing (ex: trac.cgi
don't exists at all on my server)
I also tried to use other howtos find in internet but no way.

My configuration should be:
Osx 10.6
Apache 2.2
Trac 0.12
Svn
Sqlite

I would like to know if anyone had this problems or have an updated howto
for this.

Thanks,
Cesare

PS: It's possible to install trac directly on the default osx apache or it's
a suicide ?

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.