Search


Cloud customer?
Upgrade in MyJFrog >


Working with an older version?

JFrog Artifactory 6.x
JFrog Xray 2.x
JFrog Mission Control 3.x
JFrog Distribution 1.x
JFrog Enterprise+ (Pre-Platform Release)




Overview

This page provides a guide for the different ways you can install and configure JFrog Distribution, single node and high availability. Additional information on high availability can be found here.

To install Distribution  2.x, you must first install JFrog Artifactory 7.x.

Before you install Distribution please refer to additional information on supported platforms, browsers and other requirements, and the system architecture.

Installation Steps

The installation procedure involves the following main steps:

  1. Download Distribution as per your required installer type (Docker Compose, RPM, Debian).
  2. Install Distribution either as a single node installation, or high availability cluster.
    1. Install third party dependencies (PostgreSQL and Redis database, included in the archive)
    2. Install Distribution
  3. Configure the service
    1. Connection to Artifactory (joinKey and jfrogUrl)
    2. Additional optional configuration including changing default credentials for databases
  4. Start the Service using the start scripts or OS service management.
  5. Check the Service Log to check the status of the service.


Once you have finished the set up of JFrog Distribution, continue to Configuring Distribution


Page Contents

Default Home Directory / $JFROG_HOME

The default Distribution home directory is defined according to the installation type. For additional details see the Product Directory Structure page.

Note: This guide uses $JFROG_HOME to represent the JFrog root directory containing the deployed product.

Single Node Installation

The following installation methods are supported:

Interactive Script Installation (recommended)

All install types are supported, including: Docker Compose, RPM and Debian.

The installer script provides you an interactive way to install Distribution and its dependencies. All install types are supported.

  1. Download Distribution.
  2. Extract the contents of the compressed archive and go to the extracted folder.

    tar -xvf jfrog-distribution-<version>-<compose|rpm|deb>.tar.gz
    cd jfrog-distribution-<version>-<compose|rpm|deb>

    .env file included within the Docker-Compose archive

    This .env file is used by docker-compose and is updated during installations and upgrades.

    Notice that some operating systems do not display dot files by default. If you make any changes to the file, remember to backup before an upgrade.

    OS user permissions for Linux archive

    When running Distribution, the installation script creates a user called distribution by default which must have run and execute permissions on the installation directory.

    It is recommended to extract the Distribution download file into a directory that gives run and execute permissions to all users such as /opt.

    Linux archive
    mv jfrog-distribution-<version>-linux.tar.gz /opt/
    cd /opt
    tar -xf jfrog-distribution-<version>-linux.tar.gz
    mv jfrog-distribution-<version>-linux distribution
  3. Run the installer script.
    Note: the script will prompt you with a series of mandatory inputs, including the jfrogURL (custom base URL) and joinKey.

    Docker Compose
    ./config.sh
    RPM/DEB
    ./install.sh

    Prerequisites for Linux archive

    Refer to the Prerequisites for Distribution in Linux Archive before running the install script. PostgreSQL is optional as a prerequisite, it can also be installed through install script.

    Linux archive
    distribution/app/bin/install.sh --user <user name> --group <group name> --pg-data <data directory for postgres>
    
    -h | --help                                       : [optional] display usage
    -u | --user                                       : [optional] (default: distribution) user which will be used to run the product, it will be created if its unavailable
    -g | --group                                      : [optional] (default: distribution) group which will be used to run the product, it will be created if its unavailable
    --pg-data                                         : [optional] (default: /usr/local/pgsql/data) pass the data directory for postgres installation



  4. Validate and customize the product configuration (optional), including the third party dependencies connection details and ports.
  5. Start and manage the Distribution service.

    systemd OS
    systemctl start|stop distribution.service
    systemv
    service distribution start|stop
    Docker Compose
    cd jfrog-distribution-<version>-compose
    docker-compose -p distribution up -d
    docker-compose -p distribution ps
    docker-compose -p distribution down

    Distribution can be installed and managed as a service in Linux archive installation. Refer to the Start Distribution section under Linux Archive Manual Installation for more details. 

    Linux archive
    distribution/app/bin/distribution.sh start|stop
  6. Access Distribution from your browser at: http://<jfrogUrl>/ui/, go the Distribution tab in the Application module in the UI.
  7. Check Distribution Log.

    tail -f $JFROG_HOME/distribution/var/log/console.log

    Configuring the Log Rotation of the Console Log

    The console.log file can grow quickly since all services write to it. This file is not log rotated for Darwin installations. Learn more on how to configure the log rotation.

Manual RPM Installation

The RPM installation bundles Distribution and all its dependencies. It is provided as native RPM packages, where Distribution and its dependencies must be installed separately. Use this if you are automating installations.

  1. Download Distribution.

    tar -xvf jfrog-distribution-<version>-rpm.tar.gz
    cd jfrog-distribution-<version>-rpm
  2. Extract the contents of the compressed archive, and go to the extracted folder:

  3. Install PostgreSQL.

    Already have a PostgreSQL installation? Set your PostgreSQL connection details in the Shared Configurations section of the $JFROG_HOME/distribution/var/etc/system.yaml file.

  4. Install Redis.

  5. Install Distribution. You must run as a root user.

    rpm -Uvh --replacepkgs ./distribution/distribution.rpm
  6. Customize the product configuration.
    1. Set the Artifactory connection details.
    2. Customize the PostgreSQL Database connection details. (optional)
    3. Set any additional configurations (for example: ports, node id) using the Distribution system.yaml file.
  7. Start and manage the Distribution service.

    systemd OS
    systemctl start|stop distribution.service
    systemv OS
    service distribution start|stop|status|restart
  8. Access Distribution from your browser at: http://<jfrogUrl>/ui/, go the Distribution tab in the Application module in the UI.
  9. Check Distribution Log.

    Linux
    tail -f $JFROG_HOME/distribution/var/log/console.log

Manual Debian Installation

The Debian installation bundles Distribution and all its dependencies. It is provided as native Debian packages, where Distribution and its dependencies must be installed separately. Use this if you are automating installations.

  1. Download Distribution.
  2. Extract the contents of the compressed archive, and go to the extracted folder:

    tar -xvf jfrog-distribution-<version>-deb.tar.gz
    cd jfrog-distribution-<version>-deb
  3. Install PostgreSQL.

    Already have a PostgreSQL installation? Set your PostgreSQL connection details in the Shared Configurations section of the $JFROG_HOME/distribution/var/etc/system.yaml file.

  4. Install Redis.
  5. Install Distribution. You must run as a root user.

    dpkg -i ./distribution/distribution.deb
  6. Customize the product configuration.
    1. Set the Artifactory connection details.
    2. Customize the PostgreSQL Database connection details. (optional)
    3. Set any additional configurations (for example: ports, node id) using the Distribution system.yaml file.
  7. Start and manage the Distribution service.

    systemd OS
    systemctl start|stop distribution.service
    systemv OS
    service distribution start|stop|status|restart
  8. Access Distribution from your browser at: http://<jfrogUrl>/ui/, go the Distribution tab in the Application module in the UI.
  9. Check Distribution Log.

    Linux
    tail -f $JFROG_HOME/distribution/var/log/console.log

Manual Linux Archive Installation  

Prerequisites

The following prerequisites must be installed independently of the Distribution archive installation. Please make sure to install them before staring your Distribution service.

For your convenience, they are included within the archive.

Install Steps

  1. Extract the contents of the compressed archive and move it into distribution directory.

    tar -xvf jfrog-distribution-<version>-linux.tar.gz
    mv jfrog-distribution-<version>-linux distribution

    PostgreSQL is required and must be installed before continuing with the next installation steps.

    Set your PostgreSQL connection details in the Shared Configurations section of the $JFROG_HOME/distribution/var/etc/system.yaml file.

  2. Start PostgreSQL.

  3. Customize the product configuration.
    1. Set the Artifactory connection details.
    2. Customize the PostgreSQL Database connection details. (optional)
    3. Set any additional configurations (for example: ports, node id) using the Distribution system.yaml configuration file.
  4. Start and manage the Distribution service as the user who extracted the tar.
    As a process

    Daemon Process
    distribution/app/bin/distribution.sh start

    Manage the process.

    distribution/app/bin/distribution.sh start|stop|status|restart

    As a service

    Distribution is packaged as an archive file and an install script that can be used to install it as a service running under a custom user. Currently supported on Linux systems.

    OS User Permissions

    When running Distribution as a service, the installation script creates a user called distribution (by default) which must have run and execute permissions on the installation directory.

    It is recommended to extract the Distribution download file into a directory that gives run and execute permissions to all users such as /opt.

    To install Distribution as a service, execute the following command as root: 

    User and group can be passed through distribution/var/etc/system.yaml as shared.user and shared.group. This takes precedence over values passed through the command line on install. 

    distribution/app/bin/installService.sh --user <enter user, default value is distribution> --group <enter group, default value is distribution>
    
    -u | --user                                       : [optional] (default: distribution) user which will be used to run the product, it will be created if its unavailable
    -g | --group                                      : [optional] (default: distribution) group which will be used to run the product, it will be created if its unavailable

    The user and group will be stored in distribution/var/etc/system.yaml at the end of installation.

    To manage the service, use systemd or init.d commands depending on your system. 

    Using systemd
     systemctl <start|stop|status> distribution.service
    Using init.d
    service distribution <start|stop|status>
  5. Access Distribution from your browser at: http://<jfrogUrl>/ui/, go to the Dashboard tab in the Application module in the UI.
  6. Check the Distribution Log.

    tail -f distribution/var/log/console.log

HA Installation

The following describes how to set up an Distribution HA cluster with two or more nodes. For more information, see the System Architecture.

Prerequisites

All nodes within the same Distribution HA installation must be running the same Distribution version.

Database

Distribution HA requires an external PostgreSQL database. Make sure to install it before proceeding to install the first node. There are several ways to setup PostgreSQL for redundancy. Including: HA, Load Balancing and Replication. For more information, see the PostgreSQL documentation.

Network

  • All the Distribution HA components (Distribution cluster nodes and database server) must be within the same fast LAN.

  • All the HA nodes must communicate with each other through dedicated TCP ports.

The following installation methods are supported:

RPM/Debian Installation

First node installation steps:

  1. Install the first node. The installation is identical to the single node installation. Important: make sure not to start Distribution.
  2. Configure the $JFROG_HOME/distribution/var/etc/system.yaml file with the database and first node configuration details. For example,

    First node system.yaml
    shared:
      database:
        type: postgresql
        driver: org.postgresql.Driver
        url: postgresql://<PosgreSQL_Host_IP_address>:<postgres_port>/distribution?sslmode=disable
        username: distribution
        password: password
      security:
        joinKey: <join_key>
  3. Start and manage the Distribution service.

    systemd OS
    systemctl start|stop distribution.service
    Systemv OS
    service distribution start|stop
  4. Access Distribution from your browser at: http://<jfrogUrl>/ui/, go the Distribution tab in the Application module in the UI.
  5. Check Distribution Log.

    Linux
    tail -f $JFROG_HOME/distribution/var/log/console.log

Additional node installation steps:

In order for a node to join a cluster, the node must have the same database configuration and the Master Key. Install all additional nodes using the same steps described above, with the additional steps below:

  1. Configure the $JFROG_HOME/distribution/var/etc/system.yaml file for the additional node with master key, database and active node configurations. For example,

    Additional node system.yaml
    shared:
      database:
        type: postgresql
        driver: org.postgresql.Driver
        url: postgresql://<PosgreSQL_Host_IP_address>:<postgres_port>/distribution?sslmode=disable
        username: distribution
        password: password
      security:
        joinKey: <join_key>
  2. Copy the master.key from the first node to the additional node located at $JFROG_HOME/distribution/var/etc/security/master.key.
  3. Start the additional node.

  4. Access Distribution from your browser at: http://<jfrogUrl>/ui/, go the Distribution tab in the Application module in the UI.
  5. Check Distribution Log.

    Linux
    tail -f $JFROG_HOME/distribution/var/log/console.log

Docker Compose Installation

First node installation steps:

  1. Extract the contents of the compressed archive and go to the extracted folder.

    tar -xvf jfrog-distribution-<version>-compose.tar.gz
    cd jfrog-distribution-<version>-compose.tar.gz
  2. Run the config.sh script to setup folders with required ownership.

    ./config.sh
  3. Configure the system.yaml file with the database for the first node configuration details. For example,

    First node system.yaml
    shared:
      database:
        type: postgresql
        driver: org.postgresql.Driver
        url: postgresql://<PosgreSQL_Host_IP_address>:<postgres_port>/distribution?sslmode=disable
        username: distribution
        password: password
      security:
        joinKey: <join_key>
  4. Validate and customize the product configuration (optional), including the third party dependencies connection details and ports.

  5. Start and manage Distribution using docker-compose commands.

    cd jfrog-distribution-<version>-compose
    docker-compose -p distribution logs
    docker-compose -p distribution ps
    docker-compose -p distribution up -d
    docker-compose -p distribution down
  6. Access Distribution from your browser at: http://<jfrogUrl>/ui/, go the Distribution tab in the Application module in the UI.

  7. Check Distribution Log.

    docker-compose -p distribution logs

Additional node installation steps:

  1. Extract the contents of the compressed archive and go to the extracted folder.

    tar -xvf jfrog-distribution-<version>-compose.tar.gz
    cd jfrog-distribution-<version>-compose.tar.gz
  2. Run the config.sh script to setup folders with required ownership.

    ./config.sh
  3. Configure the system.yaml file for the secondary node with master key, database and active node configurations. For example,

    Additional node system.yaml
    shared:
      database:
        type: postgresql
        driver: org.postgresql.Driver
        url: postgresql://<PosgreSQL_Host_IP_address>:<postgres_port>/distribution?sslmode=disable
        username: distribution
        password: password
      security:
        joinKey: <join_key>
  4. Copy the master.key from the first node to the additional node located at $JFROG_HOME/distribution/var/etc/security/master.key.
  5. Validate and customize the product configuration (optional), including the third party dependencies connection details and ports.

  6. Start and manage Distribution using docker-compose commands.

    cd jfrog-distribution-<version>-compose
    docker-compose -p distribution logs
    docker-compose -p distribution ps
    docker-compose -p distribution up -d
    docker-compose -p distribution down
  7. Access Distribution from your browser at: http://<jfrogUrl>/ui/, go the Distribution tab in the Application module in the UI.

  8. Check Distribution Log.

    docker-compose -p distribution logs

Product Configuration

After installing and before running Distribution, you may set the following configurations.

Where to find the system configurations?

You can configure all your system settings using the system.yaml file located in the $JFROG_HOME/distribution/var/etc folder.

If you don't have a System YAML file in your folder, copy the template available in the folder and name it system.yaml.

Artifactory Connection Details

Distribution requires a working Artifactory server and a suitable license. The Distribution connection to Artifactory requires 2 parameters:

  • jfrogUrl - URL to the machine where JFrog Artifactory is deployed, or the load balancer pointing to it. It is recommended to use DNS names rather than direct IPs. For example: "http://jfrog.acme.com or http://10.20.30.40:8082"
    Set it in the Shared Configurations section of the $JFROG_HOME/distribution/var/etc/system.yaml file.
  • join.key - This is the "secret" key required by Artifactory for registering and authenticating the Distribution server.
    You can fetch the Artifactory joinKey (join Key) from the JPD UI in the Administration module | Security | Settings | Join Key
    Set the join.key used by your Artifactory server in the Shared Configurations section of the $JFROG_HOME/distribution/var/etc/system.yaml file.

Changing PostgreSQL Database Credentials

Distribution comes bundled with a PostgreSQL Database out-of-the-box, which comes pre-configured with default credentials

To change the default credentials:

# Access PostgreSQL as the Distribution user adding the optional -W flag to invoke the password prompt
$ psql -d distribution -U distribution -W
 
# Securely change the password for user "distribution". Enter and then retype the password at the prompt.
\password distribution
 
# Verify the update was successful by logging in with the new credentials
$ psql -d distribution -U distribution -W

Set your PostgreSQL connection details in the Shared Configurations section of the $JFROG_HOME/distribution/var/etc/system.yaml file.

Changing Redis Database Credentials

Compose

To change the default credentials:

  1. Set the new password in the  $JFROG_HOME/distribution/app/third-party/redis/redis.conf file.

    requirepass <new password>
  2. Set your Redis password in the Shared Configurations section of the $JFROG_HOME/distribution/var/etc/system.yaml file.
  3. Restart all the services.

    cd jfrog-distribution-<version>-compose 
    
     docker-compose -p distribution restart

RPM/DEB

To change the default credentials:

  1. Set the new password for RPM in the /etc/redis.conf file and for Debian in the /etc/redis/redis.conf file.

    requirepass <new password>
  2. Set your Redis password in the Shared Configurations section of the $JFROG_HOME/distribution/var/etc/system.yaml file.

  3. Restart all the services.

    service distribution restart / systemctl restart distribution.service

Archive

To change the default credentials:

  1. Set the new password in the  distribution/app/third-party/redis/redis.conf file.

    requirepass <new password>
  2. Set your Redis password in the Shared Configurations section of the distribution/var/etc/system.yaml file.
  3. Restart all the services.

     distribution/app/bin/distribution.sh restart 



Installing Third Party Applications

PostgreSQL Installation

  1. Install PostgreSQL and setup the database and user (the default user is 'distribution' with password 'password', default database name is 'distribution')

    RPM
    # Run the following commands from the extracted jfrog-distribution-<version>-rpm directory.
    
    mkdir -p /var/opt/jfrog/postgres
    chmod +x ./third-party/postgresql/postgresql-*-linux-x64.run
    ./third-party/postgresql/postgresql-*.run --unattendedmodeui none --mode unattended --datadir /var/opt/jfrog/postgres --serverport 5432
    chown -R postgres:postgres /var/opt/jfrog/postgres
    
    service postgresql-10 stop
    service postgresql-10 start
    
    cd /tmp
    su postgres
    export PGPASSWORD='postgres'
    /opt/PostgreSQL/10.13/bin/psql -c "CREATE USER distribution WITH PASSWORD 'password';"
    /opt/PostgreSQL/10.13/bin/psql -c "CREATE DATABASE distribution WITH OWNER=distribution ENCODING='UTF8';"
    /opt/PostgreSQL/10.13/bin/psql -c "GRANT ALL PRIVILEGES ON DATABASE distribution TO distribution;"
    exit
    Debian
    # Run the following commands from the extracted jfrog-distribution-<version>-deb directory.
    
    mkdir -p /var/opt/jfrog/postgres
    chmod +x ./third-party/postgresql/postgresql-*-linux-x64.run
    ./third-party/postgresql/postgresql-*.run --unattendedmodeui none --mode unattended --datadir /var/opt/jfrog/postgres --serverport 5432
    chown -R postgres:postgres /var/opt/jfrog/postgres
     
    service postgresql-10 stop
    service postgresql-10 start
     
    cd /tmp
    su postgres
    export PGPASSWORD='postgres'
    /opt/PostgreSQL/10.13/bin/psql -c "CREATE USER distribution WITH PASSWORD 'password';"
    /opt/PostgreSQL/10.13/bin/psql -c "CREATE DATABASE distribution WITH OWNER=distribution ENCODING='UTF8';"
    /opt/PostgreSQL/10.13/bin/psql -c "GRANT ALL PRIVILEGES ON DATABASE distribution TO distribution;"
    exit

     

    Linux Archive
    ## The binaries are available in the folder: "distribution/app/third-party/pgsql"
     
    ## As a sudo user, create the data folders to be used by Postgres and make this user (<user_name>) the owner
    sudo su
    mkdir -p /usr/local/pgsql/data
    chown -R <user_name> /usr/local/pgsql/data
     
    ## For your convenience and to avoid Postgres failing to startup because of path issues, set the path and locale.
    su <user_name>
    LC_ALL="en_US.UTF-8"
    LC_CTYPE="en_US.UTF-8"
     
    ## Initialize the data directory
    distribution/app/third-party/pgsql/bin/initdb -D /usr/local/pgsql/data
     
    ## Start Postgres service
    distribution/app/third-party/pgsql/bin/pg_ctl -D /usr/local/pgsql/data -l ~/logfile start
     
    ## Enabling Postgres connectivity from remote servers, Will be needed only  for HA or externalised database installations
    ## Add the following line to  /usr/local/pgsql/data/pg_hba.conf
    host    all             all             0.0.0.0/0               md5
     
    ## Add the following line to /usr/local/pgsql/data/postgresql.conf
    listen_addresses='*'
     
    ## Restart Postgres service
    distribution/app/third-party/pgsql/bin/pg_ctl -D /usr/local/pgsql/data -l ~/logfile stop
    distribution/app/third-party/pgsql/bin/pg_ctl -D /usr/local/pgsql/data -l ~/logfile start
     
    # Create the psql database (the script "distribution/app/third-party/postgresql/createPostgresUsers.sh" , responsible for seeding Postgres assumes this database exists)
    distribution/app/third-party/pgsql/bin/psql template1
    <postgres prompt>: CREATE DATABASE <user_name>;
    <postgres prompt>: \q
     
    ## run the script to seed the tables and schemas needed by Distribution
    POSTGRES_PATH=distribution/app/third-party/pgsql/bin distribution/app/third-party/postgresql/createPostgresUsers.sh
  2. Configure PostgreSQL to allow external IP connections.
    By default PostgreSQL will only allow localhost clients communications. To enable different IPs to communicate with the database you will need toconfigure the pg_hba.conf file. This file can found under /var/opt/jfrog/postgres. To grant all IPs access you may add the below, under the IPv4 local connections section

    host    all             all             0.0.0.0/0               trust

Redis Installation

RPM
# Run the following commands from the extracted jfrog-distribution-<version>-rpm directory.

# Note : Use rpms with el6 when installing on Centos 6 and RHEL 6
semodule -i ./third-party/redis/distribution-redis.pp
rpm -ivh --replacepkgs ./third-party/redis/jemalloc-3.6.0-1.el7.x86_64.rpm
rpm -ivh --replacepkgs ./third-party/redis/redis-4.0.7-1.el7.remi.x86_64.rpm
service redis start

# verify if redis is working - should return PONG
redis-cli -a password ping

sed -i "s|# requirepass foobared|requirepass password|g" /etc/redis.conf

echo "appendonly yes" >> /etc/redis.conf
echo "appendfsync everysec" >> /etc/redis.conf
sysctl vm.overcommit_memory=1

service redis restart
Debian
# Run the following commands from the extracted jfrog-distribution-<version>-deb directory.

dpkg -i ./third-party/redis/redis-tools_4.0.8-1chl1_xenial1_amd64.deb
dpkg -i ./third-party/redis/redis-server_4.0.8-1chl1_xenial1_amd64.deb
service redis-server start
 
# verify if redis is working - should return PONG
redis-cli -a password ping
 
sed -i "s|# requirepass foobared|requirepass password|g" /etc/redis/redis.conf

echo "appendonly yes" >> /etc/redis/redis.conf
echo "appendfsync everysec" >> /etc/redis/redis.conf

sysctl vm.overcommit_memory=1
 
service redis-server restart

For Advanced Users

Manual Docker Compose Installation

  1. Extract the contents of the compressed archive and go to the extracted folder.

    tar -xvf jfrog-distribution-<version>-compose.tar.gz

    .env file included within the Docker-Compose archive

    This .env file is used by docker-compose and is updated during installations and upgrades.

    Notice that some operating systems do not display dot files by default. If you make any changes to the file, remember to backup before an upgrade.

  2. Create the following folder structure under JFROG_HOME.

    `-- [1020    1020  ]  var
        |-- [1020    1020  ]  data
        |   |-- [999      999  ]  postgres
        |   |   `-- [999      999  ]  data
        |   `-- [999      999  ]  redis
        |-- [1020    1020  ]  etc
  3. Copy the appropriate docker-compose templates from the templates folder to the extracted folder. Rename it as docker-compose.yaml.

    RequirementTemplate
    Distribution with externalised databasesdocker-compose.yaml
    Distribution with PostgreSQLdocker-compose-postgres.yaml
  4. Update the .env file.

    ## The Installation directory for Distribution. IF not entered, the script will prompt you for this input. Default [$HOME/.jfrog/distribution]
    ROOT_DATA_DIR=
  5. Customize the product configuration.
    1. Set the Artifactory connection details.
    2. Customize the PostgreSQL Database connection details. (optional)
    3. Set any additional configurations (for example: ports, node id) using the Distribution system.yaml file.

      Ensure the host's ID and IP are added to the system.yaml. This is important to ensure that other products and Platform Deployments can reach this instance

  6. Start Distribution using docker-compose commands.

    docker-compose -p distribution logs
    docker-compose -p distribution ps
    docker-compose -p distribution up -d
    docker-compose -p distribution down
  7. Access Artifactory from your browser at: http://SERVER_HOSTNAME/ui/. For example, on your local machine: http://localhost/ui/.

  8. Check Distribution log.

    docker-compose -p distribution logs

    Configuring the Log Rotation of the Console Log

    The console.log file can grow quickly since all services write to it. The installation scripts add a cron job to log rotate the console.log file every hour.

    This is not  done for manual Docker Compose installations. Learn more on how to configure the log rotation.


  • No labels
Copyright © 2020 JFrog Ltd.