mirror of
https://github.com/commercialhaskell/stackage-server.git
synced 2026-01-11 19:58:28 +01:00
Server for stable, curated Haskell package sets
05337cd782
Changed the protocol of the URL used as a custom search engine from `http` to `https`. The reason for this change is that `www.stackage.org` only uses `https`, so every time the custom search engine is used, a redirect from `http` to `https` occurs, sacrificing the cleanliness of the history. On `www.stackage.org`, the HTTP header is set to `strict-transport-security max-age=15724800; includeSubDomains` for HSTS, so there's no need to try connecting via http. This is a bit unclear to me as well, but even though HSTS is set and a redirect is set for subsequent access, it seems that no communication is being made, but it is left in the history. In any case, I think it's wasteful to constantly access http when it's specialized for https to the point of setting HSTS, so I'm making this commit. |
||
|---|---|---|
| .github/workflows | ||
| app | ||
| bench | ||
| config | ||
| design | ||
| docker | ||
| src | ||
| static | ||
| templates | ||
| .dir-locals.el | ||
| .dockerignore | ||
| .ghci | ||
| .gitignore | ||
| .hindent.yaml | ||
| .stylish-haskell.yaml | ||
| indices | ||
| LICENSE | ||
| package.yaml | ||
| README.md | ||
| stack.yaml | ||
stackage-server
Server for stable, curated Haskell package sets
This repo is part of the Stackage project, and the live server can be viewed at https://www.stackage.org.
Building locally
Build locally by passing the dev flag to it:
$ stack build . --flag stackage-server:dev
Simple testing with sqlite:
To test the UI without real data, just run:
$ yesod devel
(install the yesod executable from yesod-bin).
Testing with postgresql
Now, initially you need to run the cron job to create and populate the database:
$ export PGSTRING=postgresql://postgres:password@localhost:5432/stackage
$ stack exec stackage-server-cron
Note that you need to modify the PGSTRING environment variable according to your actual database configuration. Also, you need to create an empty database before running the cron job. Note that it takes quite some time for it to load your database.
After this, run the stackage server:
$ export PGSTRING=postgresql://postgres:password@localhost:5432/stackage
$ stack exec stackage-server