From 64933596f53efacf653698367fb6c908c8e3e9ea Mon Sep 17 00:00:00 2001 From: Paul Makles Date: Fri, 29 Apr 2022 16:58:11 +0100 Subject: [PATCH] chore: clean up --- .env.example | 8 ++++---- .gitignore | 8 +++++--- README.md | 11 +++++++++++ 3 files changed, 20 insertions(+), 7 deletions(-) diff --git a/.env.example b/.env.example index 25c432b..d89992f 100644 --- a/.env.example +++ b/.env.example @@ -95,11 +95,11 @@ MINIO_ROOT_USER=minioautumn # MinIO Root Password MINIO_ROOT_PASSWORD=minioautumn -# AWS Access Key ID (auto-filled if present above) -# AWS_ACCESS_KEY_ID=minioautumn +# AWS Access Key ID +AWS_ACCESS_KEY_ID=minioautumn -# AWS Secret Key (auto-filled if present above) -# AWS_SECRET_ACCESS_KEY=minioautumn +# AWS Secret Key +AWS_SECRET_ACCESS_KEY=minioautumn ## diff --git a/.gitignore b/.gitignore index 7da3c65..fe286ca 100644 --- a/.gitignore +++ b/.gitignore @@ -1,3 +1,5 @@ -data -data.old -.env \ No newline at end of file +data* + +.env + +docker-compose.override.yml diff --git a/README.md b/README.md index e473b7b..e9f4f06 100644 --- a/README.md +++ b/README.md @@ -51,6 +51,17 @@ Then bring up Revolt: docker-compose up -d ``` +## Expose Database + +You can insecurely expose the database by creating `docker-compose.override.yml` with the content: + +```yml +services: + database: + ports: + - "27017:27017" +``` + ## To-Do - Interactive setup.