You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
(12) |
Apr
(3) |
May
|
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(5) |
Oct
|
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2005 |
Jan
(3) |
Feb
(2) |
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Steven H. R. PhD. <st...@sh...> - 2003-03-25 11:34:30
|
Torbjörn Törnkvist wrote: > I just tested it, and it seem to work fine. > I added some instructions to the README file > about how to enable Yaws. > > Steven H. Rogers, PhD. wrote: > >> Is the CVS build functional. I haven't got it to fully work, though I >> suspect a configuration issue. When I try to log in with any of the >> user/passwd combinations in the configuration file, it complains that >> it can't find the user. > > > Did you run the ./bin/btt_initdb script as described in the README ? > And did you have at least one user defined in the btt.conf file ? > Yes, I added a user to btt.conf and tried that user as well as a couple of others. Regards, Steve -- _ Steven H. Rogers, PhD. <_` email: st...@sh... |_> Weblog http://shrogers.com/zope/portal/Members/steve/blog | \ "A language that doesn't affect the way you think about programming is not worth knowing." - Alan Perlis |
From: <tn...@ho...> - 2003-03-25 07:54:17
|
Steven H. Rogers, PhD. wrote: > Is the intent to only run Yaws embedded in BTT, or will it be possible > to use Yaws as an application server, with BTT being one application? > > Steve You should use the './bin/btt_yaws' script which does the latter, i.e BTT is an application of yaws. In this script, the yaws '-i' flag is used at the moment so that is makes debugging a bit easier. To have yaws running as a daemon, remove the '-i' flag and replace it with '-D -heart' . Cheers /Tobbe |
From: <tn...@ho...> - 2003-03-25 07:51:30
|
I just tested it, and it seem to work fine. I added some instructions to the README file about how to enable Yaws. Steven H. Rogers, PhD. wrote: > Is the CVS build functional. I haven't got it to fully work, though I > suspect a configuration issue. When I try to log in with any of the > user/passwd combinations in the configuration file, it complains that > it can't find the user. Did you run the ./bin/btt_initdb script as described in the README ? And did you have at least one user defined in the btt.conf file ? > > > What woudl be an appropriate testing proceedure with the CVS code? > Test in the devleopment directory or copy to a test directory? > > Regards, > Steve I usually run it in the CVS directory, which may not be a very good idea since it is easy to commit config files which has changed to suit the local install. However, I always put the 'mnesia' and 'maildir' directories somewhere else. Cheers /Tobbe |
From: Steven H. R. PhD. <st...@sh...> - 2003-03-25 03:09:47
|
Is the intent to only run Yaws embedded in BTT, or will it be possible to use Yaws as an application server, with BTT being one application? Steve -- _ Steven H. Rogers, PhD. <_` email: st...@sh... |_> Weblog http://shrogers.com/zope/portal/Members/steve/blog | \ "A language that doesn't affect the way you think about programming is not worth knowing." - Alan Perlis |
From: Steven H. R. PhD. <st...@sh...> - 2003-03-25 03:07:32
|
Is the CVS build functional. I haven't got it to fully work, though I suspect a configuration issue. When I try to log in with any of the user/passwd combinations in the configuration file, it complains that it can't find the user. What woudl be an appropriate testing proceedure with the CVS code? Test in the devleopment directory or copy to a test directory? Regards, Steve -- _ Steven H. Rogers, PhD. <_` email: st...@sh... |_> Weblog http://shrogers.com/zope/portal/Members/steve/blog | \ "A language that doesn't affect the way you think about programming is not worth knowing." - Alan Perlis |
From: <tn...@ho...> - 2003-03-12 10:41:08
|
Well, my plan is to: + Convert fully to Yaws. + Convert fully to the new look. + Maintenance. If someone else want to add new stuff it is fine by me. However, I think the main policy should be: "Keep is simple". Cheers /Tobbe =20 Mickael Remond wrote: >Torbj=F6rn T=F6rnkvist <tn...@ho...>: > > =20 > >>Hi, >> >>Since the developers of BTT now has doubled :-) I wanted >>to inform you that I have created a BTT developers mailing >>list. The intention is (of course) to use it when discussing >>things concerning the development of BTT. >> =20 >> > >What I did recently was make sure that the code was properly building. >I made sure that the default target was the previous version, until we m= anage >make the new version completly work. > >What are you, guys, your long term idea regarging the BTT tools ? > > =20 > |
From: <tn...@ho...> - 2003-03-12 07:28:09
|
Uups...forgot to do an reply-all. |
From: Steven H. R. PhD. <st...@sh...> - 2003-03-12 03:30:27
|
I'm extending BTT to provide equipment downtime/issue tracking. The equipment that I'm interested in has mechancical, electronic, and software components, so something that works for me should be pretty generally useful. More generally, this can be used for service downtime. Downtime tickets are similar to, but somewhat different than the issue tickets in the present incarnation of BTT. This can be implemented either as a seperate table or by adding/overloading fields to the ticket table. I'm inclinde to create a new table. Any thoughts? Here are the fields that I'm thinking of: -record(downtime_ticket, {id, % Unique ticket ID number location, % Physical location or URL? downtime, % Date and time that system went down uptime, % Date and time that system returned to service author, % Creator of ticket product % System type system_id, % Unique to location component, % Component info type, % Type of downtime, e.g. upgrade, failure subtype, % e.g. electrical, mechanical, software solution, % e.g. replaced component, rebooted impact % other systems affected text}). % additional comments Regards, Steve -- _ Steven H. Rogers, PhD. <_` email: st...@sh... |_> Weblog http://shrogers.com/zope/portal/Members/steve/blog | \ "A language that doesn't affect the way you think about programming is not worth knowing." - Alan Perlis |