| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Otherwise, concurrent requests can cause the output to be interleaved.
|
| | |
|
| |
|
|
|
| |
This'll help the a service manager (like the shepherd) know when the service
is ready, which at the moment, means the database migrations have happened.
|
| |
|
|
| |
As this means it can find the relevant files.
|
| |
|
|
| |
So that it can always find psql.
|
| | |
|
| | |
|
| |
|
|
|
| |
Install the assets and sqitch files, as they are needed. Remove the test
related sources.
|
| |
|
|
|
|
| |
This runs Sqitch on startup, which should make managing the database easier,
as you just have to restart the service with this option, and the database
should be updated if necessary.
|
| |
|
|
|
|
| |
This indicates currently if the database is accessible and a simple query can
be performed. I'm mostly looking at using this when writing a system test for
this service.
|
| |
|
|
|
|
|
|
|
| |
Previously, one of the first things that happened when responding to a request
was a database connection was made, even when serving the CSS. This is
unnecessary, so move the database connection handling in to the controller.
Also, to allow for separating it out from the assets, separate the assets out
from the parts of the controller that require a database connection.
|
| | |
|
| |
|
|
|
|
|
|
| |
Create a new events table for the new guix revision jobs, and update this when
processing a job starts, as well as finished with success or failure.
Additionally, remove the dependnency on open-inferior/container, as this
functionality isn't merged in to Guix master yet.
|
| |
|
|
|
|
|
| |
Previously, the records for jobs would be deleted. It's useful to know when
jobs were inserted in to the database, as well as when they succeeded (if they
have). This change also makes it possible to keep track of jobs that have
failed, as they won't be deleted.
|
| | |
|
| |
|
|
| |
It now actually looks at the fields which have been provided.
|
| | |
|
| |
|
|
| |
As previously the pages would render, but with no data.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Where there are multiple interrelated fields, then it's useful to only apply
the default if another field hasn't been specified.
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
To get git repository and git branch information suitable for the revision
page.
|
| |
|
|
| |
This is useful for some queries with duplicated parts of the results.
|
| |
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
Previously, the timezone was stripped off, so the timestamps were off. This
commit changes the code to use a Unix timestamp, which avoids this issue.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
On one code path, they were handled as numbers, whereas elsewhere they were
handled as strings. This led to the package-metadata code trying to insert
duplicate entries.
Instead, just handle them as strings everywhere.
|
| |
|
|
| |
So at least they're stable.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
I'm thinking about adding more fields to this table, and the sha1_hash values
will make this tricker.
Therefore, remove the value, and adjust the existing code to cope. This commit
also adds a new test which coveres some of the changed functionality.
|
| |
|
|
| |
This to help test code which uses the (guix inferior) module.
|
| |
|
|
|
| |
Using the test driver from build-aux/test-driver.scm, as this shows the test
errors when tests fail.
|
| | |
|
| | |
|