ArtOfCode

@quartata or you just convert config to yaml, which would be far easier and not require us to port in a whole new system

That file does get written a lot, but even so, 20G/day seems excessive. Not sure what's going on there.

Sure, but 2M per write also seems excessive. I'm sure it's not meant to be logging that much data.

_Definitely_ excessive. Each API call should only be logging a few values - the number of seconds spent in the queue for each post in that site's queue, which is...

The other way to do a lot of this, particularly for things that aren't likely to change often (or at all), would be to add a config file in the...

> We've got a fix in [codidact/co-design#66](https://github.com/codidact/co-design/pull/66) ready to go. > > After co-design is shipped with the new value (i.e. PR above is merged and new NPM release made),...

This is a good one for someone new - either new to developing, to Ruby, or to the project. It's nice and isolated, with few changes required to existing views....

That guide has more detail than the README, so that should work for you @Trilarion. We don't specifically need 2.6.6, but that's the version it's built with so that's the...

@Trilarion the routes will be a tricky one. codidact.com is currently a static site, not served by QPixel. I think for the moment we'll need to create the network profile...

As a mod/admin you can see _deleted_ user's profiles, not _destroyed_ users. The former is a soft-delete; the latter is completely removed from the database. That said, completely destroying a...