mkdirs.cfg #2

  • //
  • guest/
  • perforce_software/
  • sdp/
  • main/
  • Server/
  • Unix/
  • setup/
  • mkdirs.cfg
  • View
  • Commits
  • Open Download .zip Download (4 KB)
# CONFIGURATION VARIABLES:
#
# Do not prefix these paths with a /
# Make sure these volumes exist in the filesystem.
# DB1 = Root metadata during install. Paths will switch during recreate_db_checkpoint.sh run.
# DB2 = Offline metadata during install
# If you do not have separate volumes for root and offline, just set DB1 and DB2 to the same volume.
DB1=hxmetadata1
DB2=hxmetadata2
DD=hxdepots
LG=hxlogs
# CN is the volume for /p4/common. It is separated here so that you can set it to a different
# volume if you are installing other instances on different depots volumes than where the
# common folder is located.
CN=$DD

# The SDP is typically on the same volume as the common folder, so we default to that volume.
SDP=/$CN/sdp

# If you are sharing the depotdata volume with a replica, change this value to TRUE
SHAREDDATA=FALSE

OSUSER=perforce
OSGROUP=perforce

# CASE_SENSITIVE settings:
# 0 -- Server will run '-C1' mode, forcing case-insensitive mode on normally case-sensitive platforms
# 1 -- Server will run with case sensitivity default of the underlying platform (Unix is case sensitive).

CASE_SENSITIVE=1

# Admin user's account name.
ADMINUSER=perforce

# Admin user's password
P4ADMINPASS=adminpass

# Email address from which emails are sent.  This must be exactly one email address.  Depending on the
# configuration of the email server, it may or may not be a distribution list.  More strict email
# server configurations require it to be an email associated with an individual account.
MAILFROM="admin@example.com"

# Email to receive emails from SDP scripts. This can be a comma-separated list and/or contain a distribution
# list email (e.g. PerforceAdmin@MyCompany.com). If you want something other than $MAILFROM, just 
# remove $MAILFROM and create your own list in quotes.
MAILTO=$MAILFROM

# Mail Host Address
MAILHOST=mail.example.com

# SSL_PREFIX should be blank to not use SSL, otherwise ssl:
#
# If you are planning to use SSL, you need to put certificates in /p4/ssl after the SDP install or
# you can generate a self signed certificate as follows:
# Edit /p4/ssl/config.txt to put in the info. for your company.
# Then run: /p4/common/bin/p4master_run <instance> /p4/<instance>/p4d_<instance> -Gc
# For example using instance 1:
# /p4/common/bin/p4master_run 1 /p4/1/bin/p4d_1 -Gc
#
SSL_PREFIX=ssl:

# Set MASTERINSTANCE to the first instance in your installation.
# This is used for linking the license and ssl dir to the other instances to avoid duplication.
MASTERINSTANCE=1

P4_PORT=${SDP_INSTANCE}666
P4BROKER_PORT=${SDP_INSTANCE}667
P4WEB_PORT=808${SDP_INSTANCE}
P4FTP_PORT=202${SDP_INSTANCE}

# If you're SDP_INSTANCE is non numeric, then uncomment the items below to set the PORT setting.
# Port for this Perforce server to listen on.
# P4_PORT=1666

# Ignore the broker port if you are not running a broker.
# P4BROKER_PORT=1667
# P4WEB_PORT=80
# P4FTP_PORT=21

# DNS Name or IP address of master or edge server
# A DNS Name is much easier to manage for failover purposes.
P4DNSNAME=DNS_name_of_master_server

# Replication service user's password
P4SERVICEPASS=servicepass

# The server.id of the master server.  Or, if configuring
# an edge server or replica of an edge server, set this
# to the server.id of the edge server.
MASTER_ID=master.${SDP_INSTANCE}

# Replica server.id name
REPLICA_ID=replica

# Replica TRUE or FALSE setting
# This should be FALSE for commit and edge servers since they both run like a master server.
# It should also be FALSE on a proxy server so that the server.id file will match the master
# setting and p4_<instance>_vars will not create an empty database by running the -cshow commands.
REPLICA_TF=FALSE

# Email address for p4review complaints for each instance
# look something like P4Review_1666@example.com.  Set
# the COMPLAINFROM_PREFIX (e.g. "P4Review") and
# COMPLAINFROM_DOMAIN (e.g. "example.com)" here.  Instance
# specific values are substituted below.
COMPLAINFROM_DOMAIN=example.com
COMPLAINFROM="${SSL_PREFIX}${P4DNSNAME}:${P4_PORT}_P4Review\@${COMPLAINFROM_DOMAIN}"
# Change User Description Committed
#10 28858 C. Thomas Tyler Released SDP 2022.1.28855 (2022/05/27).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#9 28240 C. Thomas Tyler Released SDP 2021.1.28238 (2021/11/12).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#8 27761 C. Thomas Tyler Released SDP 2020.1.27759 (2021/05/07).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#7 27331 C. Thomas Tyler Released SDP 2020.1.27325 (2021/01/29).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#6 25380 C. Thomas Tyler Released SDP 2019.1.25374 (2019/03/21).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#5 25245 C. Thomas Tyler Released SDP 2019.1.25238 (2019/03/02).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#4 23331 C. Thomas Tyler Released SDP 2017.4.23329 (2017/12/05).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#3 22950 akwan Provide an override for difference between proxy listening port and target port
#2 22685 Russell C. Jackson (Rusty) Update main with current changes from dev.
#1 22185 C. Thomas Tyler Released SDP 2017.2.22177 (2017/05/17).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
//guest/perforce_software/sdp/dev/Server/Unix/setup/mkdirs.cfg
#2 22145 Robert Cowham Update mkdirs to help testing.
#1 22070 Russell C. Jackson (Rusty) Pull the configuration items out into mkdirs.cfg and source that file
in mkdirs.sh. Makes it a little cleaner, and less likely for someone
to mess up the mkdirs.sh script. Also preps for potential future
configure_sdp.sh script to ask questions and create the mkdirs.cfg file.