libre.sh/keycloak-scim
2
0
Fork 0
Code Issues 14 Pull requests Releases Packages Activity Actions 6

KEYCLOAK-5354 update READMEs (#4443)

Browse source
This commit is contained in:
vramik 2017-08-30 11:55:52 +02:00 committed by Stian Thorgersen
parent 8bfab22417
commit 0570e6e218
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -38,7 +38,7 @@ Starting Keycloak
To start Keycloak during development first build as specified above, then run: To start Keycloak during development first build as specified above, then run:
mvn -f testsuite/integration-deprecated/pom.xml exec:java -Pkeycloak-server mvn -f testsuite/utils/pom.xml exec:java -Pkeycloak-server
To start Keycloak from the server distribution first build the distribution it as specified above, then run: To start Keycloak from the server distribution first build the distribution it as specified above, then run:

6
misc/UpdatingDatabaseSchema.md
View file

@ -35,7 +35,7 @@ You can also have Liquibase and Hibernate create one for you. To do this follow
3. Make a copy of the database: 3. Make a copy of the database:
`cp keycloak.h2.db keycloak-old.h2.db` `cp keycloak.h2.db keycloak-old.h2.db`
3. Run KeycloakServer to make Hibernate update the schema: 3. Run KeycloakServer to make Hibernate update the schema:
`mvn -f testsuite/integration-deprecated/pom.xml exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='development-update'` `mvn -f testsuite/utils/pom.xml exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='development-update'`
4. Wait until server is completely started, then stop it 4. Wait until server is completely started, then stop it
5. View the difference: 5. View the difference:
`mvn -f connections/jpa-liquibase/pom.xml liquibase:diff -Durl=jdbc:h2:keycloak-old -DreferenceUrl=jdbc:h2:keycloak` `mvn -f connections/jpa-liquibase/pom.xml liquibase:diff -Durl=jdbc:h2:keycloak-old -DreferenceUrl=jdbc:h2:keycloak`
@ -50,11 +50,11 @@ add entries to the `change-set` to update existing data if required.
When you have update the change-set Hibernate can validate the schema for you. First run: When you have update the change-set Hibernate can validate the schema for you. First run:
rm -rf keycloak*h2.db rm -rf keycloak*h2.db
mvn -f testsuite/integration-deprecated exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='update' mvn -f testsuite/utils/pom.xml exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='update'
Once the server has started fully, stop it and run: Once the server has started fully, stop it and run:
mvn -f testsuite/integration-deprecated exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='development-validate' mvn -f testsuite/utils/pom.xml exec:java -Pkeycloak-server -Dkeycloak.connectionsJpa.url='jdbc:h2:keycloak' -Dkeycloak.connectionsJpa.databaseSchema='development-validate'
Testing database migration Testing database migration