Gecko [ v99win.today ]

Name	Size	Permission
.placeholder	102 B	-rw-r--r--
cpanel-analytics	129 B	-rw-------
cpanel_autossl	77 B	-rw-------
e2scrub_all	201 B	-rw-r--r--
imunify-antivirus	792 B	-rw-r--r--
imunify-notifier	144 B	-rw-r--r--
imunify_scan_schedule	129 B	-rw-------
mailman	2.05 KB	-rw-r--r--
popularity-contest	191 B	-rw-r--r--
sync	162 B	-rw-r--r--
sysctl	104 B	-rw-r--r--
sysstat	396 B	-rw-r--r--
wp-toolkit-update	1.26 KB	-rw-r--r--

Code Editor : wp-toolkit-update

# This cronjob is responsible for receiving the updates of WP Toolkit.
# It works as following logic:
# - WPT CLI is called to receive the available update version;
# - If update is found, then the URLs to the host with repositories are updated and cache is cleared for WPT repos;
# - If WPT CLI is failed (e.g. unable to communicate with update service or WPT is completely broken), then
# the cronjob executes wp-toolkit-installer script to set the default URLs to host with repositories;
# - Finally the package manager is called to install latest available version.

# Installation of WP Toolkit package always should overwrite configs,
# this allow to deliver fixes for these files without manual actions from server' admins,
# to do that the Dpkg option 'force-confnew' is used.

0 1 * * * root sleep $((1 + RANDOM \% 5))h $((1 + RANDOM \% 60))m; /usr/local/bin/wp-toolkit update-configuration > /dev/null 2> /dev/null || /usr/local/cpanel/3rdparty/wp-toolkit/bin/wp-toolkit-installer.sh --generate-configs > /dev/null 2> /dev/null; DEBIAN_FRONTEND=noninteractive LANG=C /usr/bin/apt-get --assume-yes --no-reinstall -o Dpkg::Options::="--force-confnew" install "wp-toolkit-cpanel" > /dev/null 2> /dev/null

${this.title}

Code Editor : wp-toolkit-update