| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| |\
| |
| | |
Add netcup logo to page footer
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Fix faulty regex filters in migration 59
|
| |/
|
| |
Migration 59 populated the filters table with regex filters, some of which were faulty because the `\b` character wasn't escaped. This is fixed in this PR by making all patterns raw strings.
|
| |\
| |
| | |
offtopicnames active attribute and support for PUT and PATCH request
|
| | |\
| |/
|/| |
|
| |\ \ |
|
| |/ /
| |
| |
| | |
Thanks to a recent database maintenance (https://pythondiscord.freshstatus.io/incident/139811) querying out metricity message data is far cheaper. So there is no longer a reason to only fetch blocks if the member has a low message count.
|
| |\ \ |
|
| |/ /
| |
| |
| |
| |
| | |
This was changed due to performance reasons, but after some tweaking in the database, such as increasing work memory and adding an index, this query runs much faster now.
To test this, I want to revert this change, so that we can stop the materialised view from refreshing, to see if the act of refreshing is what's causing this query to seem faster when runing against the database.
|
| |\ \
| | |
| | | |
Bump drf up to 3.12.0
|
| |/ /
| |
| |
| | |
This is to add support for Django 3.1's database-agnositic JSONField.
|
| | | |
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Bump django from 3.1.13 to 3.1.14
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
Use new approx message count view
|
| | |\ \ \
| |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We have added a new view to metricity that will keep track of an approximate message count, updating every 10 seconds.
By doing this, we avoid running a query against the whole message table every time we want to get a user's messages.
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bumps [django](https://github.com/django/django) from 3.1.13 to 3.1.14.
- [Release notes](https://github.com/django/django/releases)
- [Commits](https://github.com/django/django/compare/3.1.13...3.1.14)
---
updated-dependencies:
- dependency-name: django
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <[email protected]>
|
| |\ \ \
| |/ /
|/| | |
Bump django from 3.0.14 to 3.1.13
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \ |
|
| |/ / / |
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bumps [django](https://github.com/django/django) from 3.0.14 to 3.1.13.
- [Release notes](https://github.com/django/django/releases)
- [Commits](https://github.com/django/django/compare/3.0.14...3.1.13)
---
updated-dependencies:
- dependency-name: django
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <[email protected]>
|
| |\ \
| | |
| | | |
Clean Up Static Deployment Docs
|
| | | |
| | |
| | | |
Reorganize the static deploy readme, and clarify the content.
|
| |/ / |
|
| |\ \
| | |
| | | |
Create a signal to unassign roles from user when the role is deleted
|
| | | |
| | |
| | |
| | |
| | | |
From now on the signal will only get executed after the Role has been deleted
The commit also introduces minor changes in the tests of roles
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Create a test that checks if a role gets deleted it will also get unassigned from the user
|
| |/ /
| |
| |
| |
| | |
Add a signal to the api app that automatically unassigns
deleted roles from users that have them
|
| |\ \
| | |
| | | |
Improve Gitpod section in Sir Lancebot contributing guide
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
Adds Redirects To Static Builds
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | | |
Alter message query to leverage index
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously this query would convert each row to an array just to check if it matched or not. By changing EXCLUDE_CHANNELS to a tuple instead of a list, it doesn't get passed as an array, so we can do a simple NOT IN check.
This will also allow us to add an index with this condition to speed it up further.
|