From ee7769c8c793418264191eec0a3f88ec43f9ada1 Mon Sep 17 00:00:00 2001 From: Nick Jennings Date: Fri, 23 Jun 2023 17:21:52 +0200 Subject: [PATCH] Update readme with simplified usage --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f14c3de..d117b02 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,6 @@ so: 1. Make sure [Docker Compose is installed][1] and Docker is running (included in Docker Desktop) -2. Uncomment the `redis`, `web`, and `sidekiq` sections in `docker-compose.yml` 3. Run `docker compose up` and wait until 389ds announces its successful start in the log output 4. `docker-compose exec ldap dsconf localhost backend create --suffix="dc=kosmos,dc=org" --be-name="dev"` @@ -56,9 +55,12 @@ Running all specs: There is a working Docker Compose config file, which allows you to spin up both an app server for Rails as well as a local 389ds (LDAP) server. -By default, `docker-compose up` will only start the LDAP server, listening on -port 389 on your machine. Uncomment other services in `docker-compose.yml` if -you want to use them. +For Rails developers, you probably just want to start the LDAP server: `docker-compose up ldap`, +listening on +port 389 on your machine. + +You can pick and choose your services adding them by name (listed in `docker-compose.yml`) at +the end of the docker compose command. eg. `docker compose up ldap redis` #### LDAP server