This service caches API requests to reduce latency and reduce database load.
cd services/caches
cp .env.example .env
- Configure your
.env
according to the Env vars table below. - You should have already configured and started the Docker services. Open http://localhost:15672 in a web browser and log in with the default username and password, both
admin
. - Now, create the user that the caches service will use to access RabbitMQ. Go to the Admin tab and add a new user with username
services/caches
and password1234
. Click the username of the newly-created user, and then click the Set Permission button. This gives the user unrestricted read/write access.- You can choose a different username and password, but you will need to update the
RABBITMQ_USERNAME
andRABBITMQ_PASSWORD
in.env
to match.
- You can choose a different username and password, but you will need to update the
Now return to the main README.
Name | Purpose | Example |
---|---|---|
REDIS_URL | The URI to your redis server. Heroku sets this automatically. | redis://localhost:6379 |
REDIS_KEY | socket.io |
|
AUTH0_API_DOMAIN | As per other parts of Midspace; see services/actions/.env |
dev-xxxxx.us.auth0.com |
CORS_ORIGIN | As per other parts of Midspace; see services/actions/.env |
|
HASURA_ADMIN_SECRET | As per other parts of Midspace; see services/actions/.env |
|
GRAPHQL_API_SECURE_PROTOCOLS | As per other parts of Midspace; see services/actions/.env |
|
GRAPHQL_API_DOMAIN | As per other parts of Midspace; see services/actions/.env |
|
EVENT_SECRET | As per other parts of Midspace; see services/actions/.env |
|
RABBITMQ_USERNAME | services/caches |
|
RABBITMQ_PASSWORD | 1234 |