1
1
mirror of https://github.com/aelve/guide.git synced 2024-11-22 11:33:34 +03:00
A workspace for research teams
Go to file
avele f0f9c458a5
Front/fix/category sections enabling (#335)
* Formatting

* Category sections enabling fixes #317;
Warning when disabling editing secitons;

* Removed unused import
2019-07-13 17:29:23 +04:00
back Simplify client types (#332) 2019-07-12 18:05:34 +03:00
docker Add libpq to Docker image dependencies (#334) 2019-07-12 20:48:40 +03:00
favicon Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
front Front/fix/category sections enabling (#335) 2019-07-13 17:29:23 +04:00
scripts Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
.gitignore Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
.hlint.yaml Add HLint rules and fix some suggestions (#261) 2019-01-23 09:29:39 +01:00
.travis.yml Use travis_retry with stack setup (#330) 2019-07-11 19:10:42 +03:00
INSTALL.md Create tables with hasql (#328) 2019-07-11 22:12:14 +05:00
Makefile Migrate to LTS 13 and Ubuntu Xenial (#302) 2019-06-26 11:35:52 +03:00
README.md Create tables with hasql (#328) 2019-07-11 22:12:14 +05:00
shell.nix Create tables with hasql (#328) 2019-07-11 22:12:14 +05:00
stack.yaml Create tables with hasql (#328) 2019-07-11 22:12:14 +05:00

Aelve Guide

BSD3 license

The beta version is running at guide.aelve.com. The most complete section yet is the one about lenses.

Installation instructions and the explanation of config variables (in config.json) are here: INSTALL.md.

Contributing

If you want to contribute but don't know where to start, grep the source for [very-easy] and [easy], or look at these issues:

  • “your first pull request” really easy things, with detailed “how to fix it” instructions
  • “your second pull request” less easy things, which assume that you already know where stuff happens in the code
  • “not-fleshed-out idea” discussion issues (“should we have users? what better ways are there to present pros and cons?”) which you can help with even if you don't know Haskell
  • “design” issues about design (which I'm not good at, and so help is wanted)

Testing

You need chromedriver and selenium-server-standalone installed (those are the package names on Arch Linux). Then you can do

$ java -jar /usr/share/selenium-server/selenium-server-standalone.jar
$ make back/test

Notes

When you see something like

-- See Note [acid-state]

it means that there's an extensive comment somewhere else in the code, which you can find by grepping for Note [acid-state]. This convention was stolen from GHC. If you know some plugin for Emacs that would help with jumping to comments (even if those comments would have to be formatted differently), let me know.