-
Notifications
You must be signed in to change notification settings - Fork 3
Setting up a development environment
E. Lynette Rayle edited this page Mar 17, 2021
·
1 revision
$ git clone https://github.com/LD4P/qa_server_container.git
$ cd qa_server_container
- create a
.env
file by copying.env.example
and renaming to.env
- edit
.env
- update anything marked CHANGEME
- change other environment variables if needed
- determine a path outside the application that can hold the configurations (e.g.
/Users/_YOUR_USER_/docker/volume/authorities
) - edit
.env
and setAUTHORITIES_PATH
to that path - create
linked_data
subdirectory - copy or create configurations for the authorities you wish to make available
- create
scenarios
subdirectory underlinked_data
to hold validation tests - copy or create validations for each authority
There are a number of pre-configured authorities at LD4P/linked_data_authorities. Some of these require a cache of the data. A few are able to make direct access through the authority provider's API. This information is documented at LD4P/linked_data_authorities.
Run app with Docker by executing these commands from the root directory of the app
$ docker-compose build
$ docker-compose up
$ docker-compose down