Go to file
Alp Mestanogullari a386dd2095 point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
doc point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
nix add a test for hoistClient 2018-04-04 01:48:48 +02:00
servant point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-client point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-client-core point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-client-ghcjs point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-conduit point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-docs point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-foreign point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-http-streams point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-machines point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-pipes point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
servant-server point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
.gitignore Refactor servant-client-core 2019-02-18 19:08:13 +02:00
.stylish-haskell.yaml Reformat servant 2018-03-11 17:58:31 +02:00
.travis.yml Re-enable some recipes (servant-0.16) 2019-02-28 12:48:37 +02:00
CONTRIBUTING.md Bump docs dependencies and move docs docs to README 2019-02-12 13:38:25 +07:00
Makefile Bump versions to 0.16 2019-02-20 19:06:10 +02:00
README.md point to www.servant.dev (website) and docs.servant.dev (self-explanatory) 2019-03-02 10:08:03 +01:00
cabal.ghcjs.project Refactor servant-client-core 2019-02-18 19:08:13 +02:00
cabal.haskell-ci Update travis once again 2019-02-12 01:33:30 +02:00
cabal.project Re-enable some recipes (servant-0.16) 2019-02-28 12:48:37 +02:00
hlint.yaml Update hlint.yaml and fix some hints in servant and servant-server 2018-01-26 17:38:57 +02:00
servant.png Update READMEs 2015-04-20 15:48:37 +02:00
setup.py Add simple setup.py for RTD 2018-07-06 12:02:00 +03:00
sources.txt Support http-client’s CookieJar in servant-client 2018-01-26 18:45:52 +02:00
stack-ghcjs.yaml Add stack file for testing GHCJS. 2018-03-19 16:26:57 +01:00
stack.yaml Refactor servant-client-core 2019-02-18 19:08:13 +02:00
streaming-benchmark.sh Refactor Stream stuff 2018-11-05 15:48:47 +02:00

README.md

servant - A Type-Level Web DSL

servant

Getting Started

We have a tutorial that introduces the core features of servant. After this article, you should be able to write your first servant webservices, learning the rest from the haddocks' examples.

The central documentation can be found here. Other blog posts, videos and slides can be found on the website.

If you need help, drop by the IRC channel (#servant on freenode) or mailing list.

Contributing

See CONTRIBUTING.md

Release process outline (by phadej)

  • Update changelog and bump versions in master
    • git log --oneline v0.12.. | grep 'Merge pull request' is a good starting point (use correct previous release tag)
  • Create a release branch, e.g. release-0.13
    • Release branch is useful for backporting fixes from master
  • Smoke test in servant-universe
    • git submodule foreach git checkout master and git submodule foreach git pull to get newest of everything.
    • cabal new-build --enable-tests all to verify that everything builds, and cabal new-test all to run tests
      • It's a good idea to separate these steps, as tests often pass, if they compile :)
    • See cabal.project to selectively allow-newer
    • If some packages are broken, on your discretisation there are two options:
      • Fix them and make PRs: it's good idea to test against older servant version too.
      • Temporarily comment out broken package
    • If you make a commit for servant-universe, you can use it as submodule in private projects to test even more
  • When ripples are cleared out:
    • git tag -s the release
    • git push --tags
    • cabal sdist and cabal upload

travis

.travis.yml is generated using make-travis-yml tool, in multi-ghc-travis repository.

To regenerate the script use (note: atm you need to comment doc/cookbook/ packages).

runghc ~/Documents/other-haskell/multi-ghc-travis/make_travis_yml_2.hs regenerate

In case Travis jobs fail due failing build of dependency, you can temporarily add constraints to the cabal.project, and regenerate the .travis.yml. For example, the following will disallow single troublemaker-13.37 package version:

constraints:
  troublemaker <13.37 && > 13.37