This is test software 1
This repo contains the new RSD-as-a-service implementation. The service can be found at: https://research-software-directory.org
fair-software.nl recommendations | |
---|---|
(1/5) code repository | |
(2/5) source code license | |
images & docs licenses | |
(3/5) community registry | |
(4/5) citation | |
(5/5) checklist | |
overall | |
Other best practices | |
Contributor covenant | |
Contribution guidelines | |
Tests | |
Citation metadata consistency | |
Frontend | |
Backend | |
Authentication | |
Scrapers | |
End-to-end |
docker
and docker compose
V2 (see the documentation of Docker Compose) locally.make
to automate the configuration and installation process..env.example
to .env
file at the root of the project
and fill the secrets and passwords. Check if the secrets are correct.
The Makefile
will take care about creating an appropriate frontend/.env.local
from the .env
file, needed only when developing the frontend.make install
to install all dependencies and build the docker images.# Start the containers via the make file
make start
# OR directly use docker compose
docker compose up
# Stop all services via the makefile
make stop
# OR directly use docker compose
docker compose down
You can run frontend in development mode as docker a service (called frontend-dev) that enables hot reloading. By default this frontend-dev service will not be started automatically. For more detailed instructions see frontend/README.md.
# Run frontend development using docker at http://localhost:3000
make frontend-dev
# OR use docker compose directly
docker compose -f docker-compose.yml -f docker-compose.dev.yml up
It is possible to directly run the frontend too (without using a docker container). You must then have NodeJS installed, preferably v18.
# Build and install all dependencies.
make install
# Run the frontend and the documentation on localhost:3000 and localhost:3030
make dev
# Stop all services with `docker compose down`
make down
The content of this repository is licensed under several licenses. We follow the REUSE specification to indicate which license applies to the files specifically. Here are some general hints:
Apache-2.0
CC BY-4.0
CC0-1.0
For more details on the licenses, please have a look at the file headers or associated *.license
files. The terms of all used licenses are located in the LICENSES directory.