| Commit message (Collapse) | Author | Age | Lines |
|---|
| |\
| |
| | |
Add a jump_url field to the reminder model
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Set SECRET_KEY to a constant in DEBUG mode
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The SECRET_KEY in debug mode was auto-generated each time the config
file was loaded. This had the unwanted side-effect of requiring
testers to login again on the site as the SECRET_KEY had changed
during the reload process.
This commit resolves that by turning it into a constant. Since having
a constant secret results in the linting error `S105`, I have added a
specific `noqa` ignore for that.
|
| |\ \
| | |
| | | |
Add bulma content class to home page content for proper formatting.
|
| | | | |
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| | |
This make sure that the data receivied is valid
|
| | | |
|
| |/ |
|
| |
|
|
|
|
| |
This commit adds a link to the Code of Conduct to the dropdown menu
in the navbar. It does not include a direct link to the CoC policies,
which are accessible via the Code of Conduct page.
|
| |\
| |
| | |
Forgot to update base.html template with favicon changes
|
| | |\ |
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Wiki polish (RE: Allauth)
|
| | | | |
| | | |
| | | |
| | | | |
root shown
|
| | | | |
| | | |
| | | |
| | | | |
We've already got this handled in the main base template for the site.
|
| |/ / / |
|
| |\ \ \
| | | |
| | | | |
Wiki: Permissions hotfix
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| |_|/
|/| | |
Django Allauth (#201)
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
Bump PostgreSQL in compose.
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | |_|/
| |/| | |
Update favicons (rounded corners, other improvements)
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Improve homepage flex responsiveness
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This might break local PostgreSQL containers with the following error:
postgres_1 | 2019-10-11 20:01:48.772 UTC [1] FATAL: database files are incompatible with server
postgres_1 | 2019-10-11 20:01:48.772 UTC [1] DETAIL: The data directory was initialized by PostgreSQL version 11, which is not compatible with this version 12.0.
You will need to do one of the following:
- Delete the old data volume and start from scratch (simple, recommended).
As we don't have an explicit volume configured, only the one the PostgreSQL
image uses, this is as simple as running `docker-compose stop` followed by
`docker-compose rm`. Afterwards, you can restart it.
- The dump & restore route. Do this if you don't want to delete your
container data. To do this, first switch the PostgreSQL version in
`docker-compose.yml` back to `11`, then run the following commands:
docker-compose stop # Stop all containers
docker-compose start postgres # Start the database
docker-compose exec postgres pg_dumpall -U pysite > db.sql # Pull a SQL dump
docker-compose stop # Stop the containers again
docker-compose rm # Remove the containers
Now, update the PostgreSQL version in `docker-compose.yml` to `12` again,
and run the following commands:
docker-compose up -d postgres # Start the database
docker-compose exec -T postgres psql -U pysite < db.sql # Pull in the dump
rm db.sql # Cleanup garbage, if you want
If you're on Windows, then I can't help you. Sorry.
|
| | | | | | |
|
| | | | | |\
| |_|_|_|/
|/| | | | |
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | | |
Improve the landing page text
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
github.com:python-discord/site into tizzysaurus_landing_page_text
|
| | | |\ \ \ \ |
|
| | |/ / / / / |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Makes various minor changes to commas and formulations.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The new text was written by Tizzysaurus in his website cleanup
project, and lifted from his google doc.
|
| | | | | | |\
| |_|_|_|_|/
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Allow viewing log entries in the Django Admin.
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
python-discord/migrate-nominations-to-nominations-models
Migrate nominations to the new Nomination model
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Before the migration to Django, we stored meta data on a nomination,
such as the `reason` and `end_reason`, in the infraction table using
"note" infractions, using a special prefix for the `reason`.
We have since decided to move nominations out of the infraction
context by creating a special `Nomination` model. However, given the
complexity of the data migration, we did not yet migrate the old
nomination data to this new model. This commit migrates that data by performing a data migration.
The data migration works as follows:
- Query all nomination data in chronological order;
- Replay all nominations and add them to the `Nomination` model;
- Delete the now obsolete `Infraction` entry.
In addition, this commit also adds a useful string representation for
`Nomination` objects.
|
Sebastiaan Zeeff
Mark
scragly
Derek
Akarys42
Johannes Christ
ByteCommander
ByteCommander
Gareth Coles
Leon Sandøy
Leon Sandøy