ffeb70f787
It only served for a niche, admin nice-to-have informational stat without too much value but was unreasonably costly to maintain adding overhead with multiple queries added to all modifications to the fairly busy activities table. The database schema of the counter table and the activity_visibility function used for counter updates also did not know about "local" visibility (nor the recently removed "list" visibility) and misattributed them to the "direct" counter. On my small instance this nearly halved the average insert time for activiteis from 0.926 ms to 0.465 ms. |
||
|---|---|---|
| .. | ||
| docs | ||
| theme/partials | ||
| Makefile | ||
| mkdocs.yml | ||
| Pipfile | ||
| Pipfile.lock | ||
| README.md | ||
| requirements.txt | ||
Building the docs
You don't need to build and test the docs as long as you make sure the syntax is correct. But in case you do want to build the docs, feel free to do so.
# Make sure you're in the same directory as this README
# From the root of the Akkoma repo, you'll need to do
cd docs
# Optionally use a virtual environment
python3 -m venv venv
source venv/bin/activate
# Install dependencies
pip install -r requirements.txt
# Run an http server who rebuilds when files change
# Accessible on http://127.0.0.1:8000
mkdocs serve
# Build the docs
# The static html pages will have been created in the folder "site"
# You can serve them from a server by pointing your server software (nginx, apache...) to this location
mkdocs build
# To get out of the virtual environment, you do
deactivate