|
1 year ago | |
---|---|---|
app | 1 year ago | |
bin | 1 year ago | |
config | 1 year ago | |
data | 2 years ago | |
doc | 2 years ago | |
images | 1 year ago | |
lib | 1 year ago | |
public/images | 1 year ago | |
test | 1 year ago | |
vendor | 1 year ago | |
.env.test | 1 year ago | |
.gitignore | 1 year ago | |
.rubocop.yml | 2 years ago | |
.ruby-version | 1 year ago | |
.semver | 2 years ago | |
Gemfile | 1 year ago | |
Gemfile.lock | 1 year ago | |
LICENSE | 2 years ago | |
Makefile | 1 year ago | |
Procfile | 2 years ago | |
README.md | 2 years ago | |
Rakefile | 1 year ago | |
config.ru | 1 year ago | |
mapping.yml | 2 years ago |
RESTful JSON API for opening hours
TODO: Finish Make Install TODO: Provide alternative in docker
A Linux machine that supports apt, preferably a recent Ubuntu LTS.
make install
should ensure all dependencies are installed.
For machines that do not support Make, consider getting another OS, if anything, as a virtual machine.
For machines that do not have apt, we are open to help on making the
Makefile
more portable. Pull requests, suggestions and help is
welcome. The ideal situation would be where all common POSIX compliant
systems, will be able to run the Makefile and install dependencies.
Install all dependencies with
make install
Running the tests with
make test
Integration tests, or end to end tests, are tests that run expectations on the full application. It sets up, seeds and connects to a database and then makes requests through the REST HTTP interface.
These are slow, and will, nor cannot, cover all edge-cases, paths and exceptions. They cover the happy path, common situations and important features.
Currently ran inside the entire test-suite. If the suite grows too large, we will extract these and make them runnable separately.
The unit tests isolate a module and test that in isolation. Unfortunately, JavaScript, nor node, nor its ecosystem of packages are very clean and test-oriented. Many features, packages or libraries will inject their behaviour in the global namespace, making it very hard, sometimes impossible to mock or stub.
There are quite some tests, but not near as much as I would like.
Deploying depends on your environment. Anywhere where NodeJS is supported will probably run this software.
TODO: describe what config to change in order to deploy to your servers.
make deploy
TODO: introduce CONTRIBUTING.md
We use SemVer for versioning. For the versions available, see the release-tags on this repository
This project is licensed under the MIT License - see the LICENSE.md file for details
TODO: describe YoHours, openstreetmap, imposm, opening_hours etc.