[Upd] Refactor keycloak auth to directory with prefix -no-proxy

kbss-cvut · Dec 7, 2023 · a9d1650 · a9d1650
1 parent 5070ca3
commit a9d1650
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 1 deletion.
diff --git a/deploy/keycloak-auth/docker-compose.yml → ...keycloak-auth-no-proxy/docker-compose.yml b/deploy/keycloak-auth/docker-compose.yml → ...keycloak-auth-no-proxy/docker-compose.yml
diff --git a/.../keycloak-auth/keycloak/realm-export.json → ...-auth-no-proxy/keycloak/realm-export.json b/.../keycloak-auth/keycloak/realm-export.json → ...-auth-no-proxy/keycloak/realm-export.json
diff --git a/doc/setup.md b/doc/setup.md
@@ -54,7 +54,7 @@ RECORD_MANAGER_ROOT_PATH=/record-manager-example
 
 ### Set up with Keycloak Authorization
 
-The deployment is pretty much self-contained based on [docker-compose.yml](../deploy/keycloak-auth/docker-compose.yml). It sets up the corresponding repositories, imports a realm where clients
+The deployment is pretty much self-contained based on [docker-compose.yml](../deploy/keycloak-auth-no-proxy/docker-compose.yml). It sets up the corresponding repositories, imports a realm where clients
 are configured for both the Record Manager backend and frontend. All the services (except PostgreSQL used by Keycloak) 
 in the deployment export their ports to the host system, so ensure the following ports are available on your system: 
 3000, 8080, 8081, 8088.