| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/python-discord/site/issues/302
This commit makes newlines in deleted messages visible in the deleted
messages front-end and makes sure they are not stripped during the
conversion to HTML. To represent newlines, I've chosen a commonly
used symbol: `↵`.
In addition, I've kaizened the colour filter that translates integer
representations of colours to their RGB hex-value. The Discord dark
theme shows black colours (int: 0; hex: #000000) as white instead, to
make reading them against the dark background easier. This commit
makes sure our front-end displays the same behavior.
This closes #302
|
| |\
| |
| | |
Update dependency pinning
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Add new rules.
|
| |/ / |
|
| |\ \
| | |
| | | |
Remove breadcrumb truncation
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
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
|
| | | | | |
|
| |/ / / |
|
| |/ /
| |
| | |
As per discussion in #meta
|
| |/ |
|
| |
|
|
|
|
| |
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.
|