can you point to the tasks around reliability issues with this on toolforge? is it due to anything inherent with the toolforge infrastructure?

In T244307#5850284, @Krenair wrote:

can you point to the tasks around reliability issues with this on toolforge? is it due to anything inherent with the toolforge infrastructure?

T219330, T236391, and T242760, to name a few, and there are probably several relevant issues at https://github.com/wsexport/tool/issues.

I can't pinpoint exactly what about Toolforge is the issue, but I'm fairly confident it's part of it. We need to do more engineering, such as introducing a job queue. This is still doable on Toolforge but experience has shown that for high-traffic, resource-intensive tools like this, VPS is the better platform. We have many VPS tools as it is and are experienced with maintaining our own instances.

In T244307#5850284, @Krenair wrote:

can you point to the tasks around reliability issues with this on toolforge? is it due to anything inherent with the toolforge infrastructure?

There have been various tasks over the years. One of the historical problems the tool had was leaking temp files on grid engine lighttpd nodes. Another was related to headless X server usage leaving orphan processes on the grid.

I think there has been a lot of work done to the tool that has helped in the past months, but this certainly is one of the tools that has usage to justify "graduation" from Toolforge to a custom project if that is desired. wsexport is linked to by the sidebar of https://en.wikisource.org/ for all users including anons as the means to download EPUB and MOBI versions of books.

I would certainly rather see it in its own project than stuffed into the commtech project. Grab bag projects are an anti-pattern to avoid. They make community involvement difficult and instance ownership difficult to determine.

Thanks, we concur this is deserving a dedicated project. Note I just changed the requested name to wikisource, in the off-chance other related tools get bundled into the project (we also have reservations about some connotations of wsexport :)

Thank you!