The web documentation used to suffer from a problem that if a
documentation page were renamed in a newer version, any references
pointing to said documentation would be lost. For example, the feature
known as "Default Roles" was renamed to "Privileged Roles" but caused
a change in the URL.
This patch introduces the ability to create a "DocPageRedirect" by
specifying the previous name of the documentation page (e.g.
"default-roles.html") and the new name (e.g. "privileged-roles.html")
such that the continuity is preserved between versions.
- Debian: Add bullseye and sid
- Ubuntu: Add focal (20.04)
- Add arm64 architecture to each package page
- Modify examples to use PostgreSQL 12
Author: Christoph Berg <myon@debian.org>
Most of our auto-generated emails should not ask for auto replies (like
out of office messages or in particular, "held for moderation" notices
from our own list server), so set this header by default, and also the
header indicating if it's an auto submitted/auto replied message.
Specifically allow auto replies on moderation notices, since that's a
case where it might be really interesting for the moderator to see for
example an out of office message. At least for now that seems like a
good idea.
This helps to ensure readability of the new function table listings
while working around some of the generated code from DocBook
Authors: Tom Lane <tgl@sss.pgh.pa.us> and myself
As the align/valign attributets are deprecated in HTML 5 and as our
documentation generation scripts still spit these out, these selectors
will ensure compatibility, and also fix present alignment issues.
As part of ongoing changes to the structure of tables in the
documentation[1], the HTML property valign is being set to middle
in the table headers, but was not being respected in the pgweb CSS
rules.
This adjusts the table headers to respect the valign property, which
in testing works with both the latest documentation as well as previous
versions (and given most, if not all, table headers to date are not
multi-lined).
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=e894c61836e4b967f7ec65358fdaed2ba86ed238
This provides information about other projects that people can
contribute to outside of the core PostgreSQL software. Includes
descriptions of each project, how they are used, and how one can
get involved.
Authors: Andreas 'ads' Scherbaum <ads@pgug.de>, myself
With the new django, alerts are raised for everything with status 500,
not juse exceptions. This put a light on a number of places where we
were returning 500 server error code for things that are not actually
server errors. Some should be a regular 200 ok with an error message,
and others should be a permissions error.
Update to django 2.2. Also update a number of older dependencies that
were actually already incorrect before the djago upgrade, and the
deployed versions were newer, but we forgot to update the requirements
file.
This information can be useful when trying to debug issues with the
community auth and the wonders of distributed data...
No actual django model is created because django still doesn't support
multi-column primary keys. Thus no tool to use the data yet other than
psql.
This is primarily to enable the "make STYLE=website html" build
option of the PostgreSQL docs, as the pgweb docs page uses
the "base.css" file to render the documentation. By updating the
dynamic doc.css generation file, we can allow the builders of the
documentation to better preview what their documentation will look
like when it is loaded onto the website.
Presently, the dynamic "docs.css" is unused in pgweb or the core
project, and as those are the two biggest consumers of the
documentation styles, this is an apparent safe vector to make this
change.
Preivously the requirement was "should not have 50% or more" members
from a single company, which basically ruled out any organisation of two
people. This was never the intention, so instead change to say "no more
than 50%", which specifically allows for the case of exactly half.
Raising a generic exception generates a http 500 internal error and a
stackdump. Instead raising PermissionDenied appopriately turns it into a
http 403 forbidden response.
Per discussion in $THREAD, it Survey is unmaintained. While it offers
some nice user interactivity, because it is unmaintained it should not
be visible on the website.
It is only commented out, so that we can re-enable in the future. The
archives will remain available, albeit obfuscated.
Thread: https://postgr.es/m/BBF56CF4-2065-45C5-B61F-D616F0CB2743%40yesql.se
This was partially implemented through the system, and given that the
community auth system already assumes email is unique there is no need
to not expose it to the actual login process as well.
