Skip to content
A Haskell web application server.
Branch: master
Clone or download
Johan Tibell
Latest commit ee349f0 Nov 11, 2010
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Data Enumerate ByteString in chunks. Jun 24, 2009
Hyena Silence a warning Nov 11, 2010
Network Provide a runnable example Dec 19, 2009
.gitignore Added a .gitignore. Sep 14, 2008
LICENSE Added a README and LICENSE. Mar 19, 2008
README.markdown Renamed the README to indicate content Jun 24, 2009
STYLE Added a coding style guide. Jan 22, 2009
Setup.hs Added a build system. May 13, 2008
TODO Added a TODO. Sep 15, 2008
hyena.cabal Bumped version number to 0.1.0.1 Nov 11, 2010

README.markdown

Hyena

Hyena is a simple web application container that can be used to run Haskell web applications behind more robust web servers like Apache.

Contributing

Prerequisites

Make sure you read the [Haskell Style Guide] 1.

The existing code doesn't follow the style guide fully but you should follow it for all new code.

Creating patches

The preferred way of contributing changes to the project is to use Git and send the patches over email using the Git commands format-patch and send-email. Step by step instructions:

Clone the repository:

git clone http://github.com/tibbe/hyena

Make your changes:

cd hyena
$EDITOR <file>

Commit your changes in one or more commits:

git add <file>
git commit

Make sure you write a good commit message. Commit messages should contain a short summary on a separate line and, if needed, a more thorough explanation of the change. Write full sentences and use proper spelling, punctuation, and grammar. See [A Note About Git Commit Messages] 2 for more information.

You might want to use git rebase to make sure your commits correspond to nice, logical commits. Make sure whitespace only changes are kept in separate commits to ease reviewing.

Prepare the e.g. last five patches for sending:

git format-patch -5 -n

This will create one patch file per patch.

git send-email --to <maintainer> <patch files>

The maintainer is specified in the Cabal file. The maintainer will review your changes and may ask you to make changes to them. Make the changes to your local repository and use git rebase to massage them into nice, logical commits and resend the patches.

You can’t perform that action at this time.