1
1
mirror of https://github.com/aelve/guide.git synced 2024-11-27 10:10:50 +03:00
A workspace for research teams
Go to file
avele 845a7a671e
feat/category item info edit (#250)
* added search results nothing found text

* removed external spaces and lines

* Item info update
2018-12-13 16:02:37 +04:00
back Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
favicon Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
front feat/category item info edit (#250) 2018-12-13 16:02:37 +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
.travis.yml Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
INSTALL.md Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
Makefile Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
README.md Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00
shell.nix Add custom shell.nix file 2017-10-09 09:30:41 +02:00
stack.yaml Move the backend to /back/ (#240) 2018-12-09 23:02:03 +01:00

Aelve Guide

Build status 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. Don't be afraid to install it locally it's very easy! You don't need to set up any databases or anything like that, and you can get a full copy of the data from the site by simply cloning it from Github.

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.