libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases Packages Activity Actions

Minor fixes in documentation

Browse source
This commit is contained in:
mposolda 2016-06-01 17:50:46 +02:00
parent 8839a3d9e9
commit cee471b851
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
topics/database.adoc
View file

@ -4,7 +4,7 @@
{{book.project.name}} comes with its own embedded Java-based relational database called H2.
This is the default database that {{book.project.name}} will use to persist data and really only exists so that you can run the authentication
server out of the box. We highly recommend that you replace it with a more production ready external database. The H2 database
is not very viable in high concurrency situations and cannot be used in a cluster either. The purpose of this chapter is to
is not very viable in high concurrency situations and should not be used in a cluster either. The purpose of this chapter is to
show you how to connect {{book.project.name}} to a more mature database.
{{book.project.name}} uses two layered technologies to persist its relational data. The bottom layered technology is JDBC. JDBC

4
topics/manage.adoc
View file

@ -4,13 +4,13 @@
In the upcoming chapters, you'll often be provided two options for applying application server configuration changes to your deployment. You'll be
shown how to edit the _standalone.xml_ or _domain.xml_ directly. This must be done when the server (or servers) are offline.
Additionally, you may be shown how to apply config changes on a running server using the app server's command line interface ({{books.appserver.name}} CLI). This chapter discusses
Additionally, you may be shown how to apply config changes on a running server using the app server's command line interface ({{book.appserver.name}} CLI). This chapter discusses
how you will do this.
=== Start the {{book.appserver.name}} CLI
To start the {{books.appserver.name}} CLI, you need to run the `jboss-cli` script.
To start the {{book.appserver.name}} CLI, you need to run the `jboss-cli` script.
.Linux/Unix
[source]

2
topics/network/bind-address.adoc
View file

@ -19,7 +19,7 @@ $ standalone.sh -b 192.168.0.5
The `-b` switch sets the IP bind address for any public interfaces.
Alternatively, if you don't want to set the bind address at the command line, you can edit the profile configuration of your deployment.
Open up the profile configuration file (_standalone.xml or _domain.xml_ depending on your
Open up the profile configuration file (_standalone.xml_ or _domain.xml_ depending on your
<<fake/../../operating-mode.adoc#_operating-mode, operating mode>>) and look for the `interfaces` XML block.
[source,xml]