| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
Particularly to support checkboxes.
|
| |
|
|
|
|
| |
Mostly to enable passing the cache-control header.
|
|
|
|
|
|
| |
Given that the headers may be the same, regardless whether it's HTML or JSON
being sent in the body of the response, I think it makes more sense to handle
the headers in the controller.
|
| |
|
|
|
|
| |
Date and Commit were the wrong way around.
|
| |
|
| |
|
|
|
|
|
| |
This is mostly for the JSON output, as it allows much more information to be
included.
|
|
|
|
| |
To the query parameters module.
|
|
|
|
|
|
|
|
|
|
| |
And display this on the package page.
This uses a couple of new tables, and an additional field in the
package_metadata table.
Currently, the order of the licenses in the package definition isn't stored,
as I'm not sure the order in the list is significant.
|
|
|
|
|
|
|
| |
Store the location a package can be found at, and display this on the package
page.
If available, link off to the git repository containing the package.
|
| |
|
|
|
|
|
| |
This allows building more complicated forms, where some of the query
parameters don't work together.
|
|
|
|
|
| |
Lower powered devices will have problems displaying all ~9000+ packages, so
return a smaller number by default.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Previously, it was spliting versions up for the package pages. To stop this,
now it just matches the extensions it knows about (currently .html and .json).
|
|
|
|
| |
The first value should always be a list.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the routing layer handled the content negotiation, and the Accept
header was ignored. Now, the extension if one is provided in the URL is still
used, and more widely than before, but the Accept header is also taken in to
account.
This all now happens before the routing decisions are made, so the routing is
now pretty much extension independant (with the exception of the
/gnu/store/... routes).
|
|
|
|
|
| |
This adds more query parameter validation, and uses form-horizontal-control to
neaten up the view code.
|
| |
|
| |
|
| |
|
|
|
|
| |
Otherwise a URL like https://example.com? will cause this to fail.
|
|
|
|
|
|
| |
Add handling for some query parameters to the branch page. This takes
advantage of the improvements for building forms and query parameter
validation.
|
|
|
|
| |
Each input is pretty complex, and this function helps handle that complexity.
|
|
|
|
| |
These are useful for constructing HTML ids and similar things.
|
|
|
|
|
|
|
|
|
| |
The query parameters feed in to the results shown, but also forms on
pages. Validation is important to avoid errors and security issues, but it's
also important to provide appropriate feedback to the user.
This module provides some utilities and structure around handling query
parameters.
|
|
|
|
|
|
| |
Add some new pages /branches and /branch/... as well as a new git_branches
table. Also extend the email processing to enter the branch information in to
the database.
|
|
|
|
|
|
| |
Rather than just storing the URL in the guix_revisions and
load_new_guix_revision_jobs tables. This will help when storing more
information like tags and branches in the future.
|
|
|
|
| |
On the packages comparison page.
|
| |
|
|
|
|
| |
To show the total number of derivations, and guix revisions.
|
| |
|
| |
|
|
|
|
|
| |
Not sure why, but dynamic-wind was causing issues by closing the database
connection too early, but with-throw-handler seems to work OK.
|
| |
|
| |
|
|
|
|
|
| |
As this helps with the layout, especially the whitespace to the left
on smaller screens.
|
| |
|
| |
|
|
|
|
|
| |
Add support for filtering the results, and add the system and target
to the output.
|
| |
|
| |
|
| |
|
|
|
|
| |
For the new and removed package sections.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A large proportion of these changes relate to changing the way
packages relate to derivations. Previously, a package at a given
revision had a single derivation. This was OK, but didn't account for
multiple architectures.
Therefore, these changes mean that a package has multiple derivations,
depending on the system of the derivation, and the target system.
There are multiple changes, small and large to the web interface as
well. More pages link to each other, and the visual display has been
improved somewhat.
|