rahenrique / rah.collectiveaccess.boilerplate

CollectiveAccess Boilerplate, using Docker containers, with PHP, Apache and MySQL. This repository is solely intended as a starting point for a local development environment for CollectiveAccess implementations.

Hi there 👋

rah.collectiveaccess.boilerplate's Issues

Document basic GraphQL API test endpoints

We are downloading and installing a dev branch of Providence, so we can just test the new GraphQL API.
To make this more clear to the developers, and give them the basic tools to select other more stable branches and versions, we need to document the necessary changes in Dockerfile, and perhaps add a Postman collection to test the endpoints.

GraphQL API e Elasticsearch

Existem duas branchs relevantes para esta Issue:
1.7.17
dev/graphql-api

A tag 1.7.17 é a release estável atual, sem implementação da API GraphQL
A branch dev/graphql-api é uma branch de desenvolvimento, mas que contém a API GraphQL mais funcional

Será necessário criar um merge entre essas duas branches para utilizar tanto a indexação por Elasticsearch quanto a API simultaneamente, até que uma release estável contemple ambas implementações.

GraphQL 404's

I've been trying to figure out how to use the develop or dev/1.8rc5 branches to try the graphql API for the past two days, and I have it all deployed and running but when I hit either localhost:666/providence/service/Auth or localhost:666/service/Auth I get a 404. Do you have any tips for getting this to work?

Add ElasticSearch

Some CollectiveAccess installations require a ElasticSearch database to improve search performance.
We should provide a working example of ElasticSearch running on a container with this boilerplate.