Re: Write-access to wiki -- Directions on how to document

Hello rouilj,

thanks for your advice regarding source control and using a forge!

Please have a look at
https://codeberg.org/R2D2/roundup_todo_tracker_template
there is the original TODO Tracker from Nikolaus Rath with my changes
for the current roundup version 2.3.0.

I would be happy if this todo template could be integrated into
roundup.

I tested it with the steps "Install and (quick) setup" from
DESCRIPTION.org .


> 
> > 
> > I am evaluating roundup for the use as an inhouse maintenance tracker
> > for around 100 facilities / sites (hence the need for recurring tasks).
> > Currently I think the "Roundup TODO Template" (which I quickly got
> > working yesterday) is a good starting point. [...]
> > An estimate for the total numer of tasks does not exist but
> > pessimistic me thinks there may be around 100 per site, so 100 x 100
> > = 10.000
> > 
> 
> Is this per year or over the lifetime? If per year, you may want to
> consider using either the postgresql or mysql database backends. I
> have used the SQLite backend with a few thousands of issues and it
> handles it fine. If you have a complex schema however, you might have
> to migrate to one of the other db backends after a few years.
> 


Thanks for your advice! Since I have no real numbers I planned to start
with sqlite and fill the tracker step by step for each site.

How hard would an migration from sqlite to postgres be?
(Yeah, typical red flag for pain ;-) )


--
Have a fine day!

r2d2