forked from dCache/dcache
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: minor changes in the dcache minimal installation part
- Loading branch information
Showing
1 changed file
with
10 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,12 +11,11 @@ about how dCache works and explore some of the details of dCache | |
configuration and administration without being overwhelmed. As far as | ||
possible, you can simply copy the commands and end up with a working | ||
dCache. We've included some example commands that perform some basic | ||
tests, so you can have some confidence that everything is OK so far, | ||
before moving on to the next step. | ||
tests, so you can have confidence as you progress through the steps. | ||
Please note that, although this tutorial will provide you with a | ||
working dCache instance, your production instance should be more complex. There are many ways to configure | ||
working dCache instance, your production instance would be more complex as there are many ways to configure | ||
dCache. The optimal choice depends on which hardware you wish to use | ||
and how dCache's users will interact with the system. So, there is no a single recipe that will provide the optimal solution in | ||
and how dCache's users will interact with the system. There is no a single recipe that will provide the optimal solution in | ||
all cases. | ||
|
||
### Minimum System Requirements | ||
|
@@ -40,7 +39,7 @@ help you with your system specifications. Just contact us: <[email protected]>. | |
|
||
#### Software: | ||
|
||
- OpenJDK 11 (java 11 , and java 17 for dCache staring from version 10.1) | ||
- OpenJDK 11 (java 11, and java 17 for dCache staring from version 10.1) | ||
|
||
> yum install java-11-openjdk | ||
> | ||
|
@@ -74,18 +73,16 @@ First we install PostgreSQL: | |
|
||
> dnf -y install postgresql-server | ||
With the database packages installed, we can initialise the database | ||
the service. Note that we do not start the database at this point, | ||
With the database packages installed, we can initialise the database service. Note that we do not start the database at this point, | ||
as we will make some tweaks to the configuration. | ||
|
||
> postgresql-setup --initdb | ||
... | ||
|
||
[root@neic-demo-1 centos]# postgresql-setup --initdb | ||
* Initializing database in '/var/lib/pgsql/data' | ||
* Initialized, logs are in /var/lib/pgsql/initdb_postgresql.log | ||
|
||
... | ||
|
||
The simplest configuration is to allow password-less access to the database. | ||
|
||
|
@@ -102,8 +99,8 @@ host replication all 127.0.0.1/32 ident | |
host replication all ::1/128 ident | ||
``` | ||
|
||
To allow local users to access PostgreSQL without requiring a password, make sure the following three lines | ||
are the only uncommented lines in the file **/var/lib/pgsql/data/pg_hba.conf** | ||
To allow local users to access PostgreSQL without requiring a password, make sure only the following three lines | ||
are in the file **/var/lib/pgsql/data/pg_hba.conf** | ||
|
||
>vi /var/lib/pgsql/data/pg_hba.conf | ||
> | ||
|
@@ -116,8 +113,8 @@ are the only uncommented lines in the file **/var/lib/pgsql/data/pg_hba.conf** | |
``` | ||
|
||
|
||
> **NOTE**: the path to **/pg_hba.conf** is different for PostgreSQL 13 and higher versions. | ||
> It is **/var/lib/pgsql/data/pg_hba.conf** | ||
**NOTE**: the path to **/pg_hba.conf** is different for PostgreSQL 13 and higher versions. | ||
It is **/var/lib/pgsql/data/pg_hba.conf** | ||
|
||
|
||
|
||
|