LWN: Comments on "Roundup: managing issues for 20 years"

Roundup: managing issues for 20 years

rouilj — Wed, 27 Jul 2022 02:50:28 +0000

Just to close out this thread. Version 2.2.0 was released on July 13th and includes a Dockerfile that can be used with any of the database backends. It also includes a docker-compose file that will deploy it against a MySQL instance.

I am working on getting an organization enrolled in the open-source program on docker hub to deploy the 2.2.0 release.

Roundup: managing issues for 20 years

rouilj — Fri, 17 Sep 2021 15:05:57 +0000

I am not sure what you are trying to say. When using Berkeley DB, Roundup creates multiple database
files. One for each object/class and one for each journal (where all changes are tracked).

When it uses SQLite as the back end there is one database file for the permanent data. Ephemeral data: session cookies, password reset keys .... are kept in a separate dbm file.

Roundup: managing issues for 20 years

rouilj — Fri, 17 Sep 2021 15:00:05 +0000

It is on a todo list, I probably should put up an issue for it. I have never needed it as I can just run the demo mode directly from the checkout.

Are you interested in contributing a config?

Roundup: managing issues for 20 years

rouilj — Fri, 17 Sep 2021 14:57:42 +0000

Thanks for your interest. I develop my own sysadmin tracker using fossil, but I disabled the fossil issue tracker and run a roundup instance instead.

Although using it as a wiki is possible, fossil's wiki is probably a better choice.

Roundup: managing issues for 20 years

scientes — Fri, 17 Sep 2021 04:51:14 +0000

Dude, it is just one Berkley dB file.

Roundup: managing issues for 20 years

mrchapp — Wed, 15 Sep 2021 23:15:37 +0000

No docker-compose?

Roundup: managing issues for 20 years

flussence — Wed, 15 Sep 2021 21:47:46 +0000

This sounds promising, I'm surprised I didn't hear about it until now because I've looked around for tracker software a few times in the past and they've all tended toward extremes of enterprise feature checklists or missing out on basic QoL.

Recently I was looking for something to use as a local wiki and tracker, and ended up going with Fossil. That has an unbeatable featureset-to-weight ratio, but it really wasn't designed with customisation in mind. Roundup looks like it does much better in that area.