Added the possibility to delete single posts or a range of multiple posts at once using the command as following:<br/>
`docker-compose run server ./szuru-admin --delete posts 35 36 40-45`<br/>
Each space represents a single post id, using a `-` between two ids will delete all posts within range, including the first and the last one
Added the possibility to delete single posts or a range of multiple posts at once using the command as following:<br/>
`docker-compose run server ./szuru-admin --delete posts 35 36 40-45`<br/>
Each space represents a single post id, using a `-` between two ids will delete all posts within range, including the first and the last one
This should fix most scaling problems without needing to start
more server instances. By default, waitress maintains at most
4 threads. This works fine if the database is small (sub 100k posts)
but causes a large Task queue depth to occur if the database is larger.
Letting users increase the amount of threads means that one server instance
is able to handle more requests without locking up the rest of the site.
This adds a new environment variable to .env, THREADS, which can be used to
configure the amount of threads to start and is by default set to 4
(the default amount used by waitress).
* `test_modify_saves_non_empty_diffs` needs non-transactional
db, so moved to seperate file
* Replaced incompatable usage of `db.session.rollback()`
with parametrerized function calls
* xfail conditionals for search removed, as we can no longer
get current driver with binds
* Also remove usage of deprecated `pytest.yield_fixture`
Furthermore, an update to Pillow has improved the floating-point
precision of the image hash algorithm, requiring minor updates to
the respective unit tests.
See https://github.com/python-pillow/Pillow/pull/4320
