Skip to main content

Introducing ‘plesk installer’ (Linux)

Have you ever felt that using Parallels Installer from command line is somewhat daunting? It has a lot of options and you usually need to get required “spell” from KB articles or official forums. For example, to manually install latest updates onto your system previously you would have to run (tediously typing each option!):

No more! Introducing installer subcommand for plesk command-line hub.

We’ve already introduced plesk command-line hub in one of the previous posts. It facilitates working with Plesk utilities from shell. Starting from Plesk 11.5.30 update 12 ‘plesk installer‘ will provide you with useful shortcuts and tab-completion for Parallels Installer options. Observe:

You can also simply run plesk installer which is equivalent to running /usr/local/psa/admin/sbin/autoinstaller.

However tab-completion is just a convenience. We don’t believe many users actually type Parallels Installer commands too often. What you might find really useful is a couple of shortcuts for Parallels Installer.

This simple command will install all available updates within current Plesk version. Don’t worry, Plesk will not be accidentally upgraded to the next version with this command.

This command will do the same, but install only Plesk updates instead. I.e., system components such as MySQL and PHP will not be updated unless it is required for proper Plesk functioning. This is useful if you want to keep your system stable and has similar effect to disabling “Automatically install updates for third-party components” in Tools & Settings > Update and Upgrade Settings in Panel. This command will also reinstall latest patch for Plesk if latest update is already installed.

We recommend this command for manual installation of micro-updates.

 

Please note that plesk tool is open for further improvement based on your suggestions. Even more — the tool is open source and you can directly contribute to its development! And one last hint: the tool will (partially) work even on older Plesk versions, just follow instructions on the github page.

2 thoughts

  1. David -

    A good update to autoinstaller is to specify time to run for each container. Or specify to autoupdate one container at a time instead of the current method of starting auto installer process for each container at the same time (which causes major resource issues)

    Reply

    Sergey Lystsev -

    Generally updates are randomized over a week, so they shouldn’t update all at the same time. Virtuozzo itself shall randomize daily tasks within 6 hours timeframe. However if you would want to control additionally within a day, you can play with cron settings and edit /etc/crontab for setting comfortable time for daily and weekly tasks:

    SHELL=/bin/bash
    PATH=/sbin:/bin:/usr/sbin:/usr/bin
    MAILTO=root
    HOME=/

    # run-parts
    37 * * * * root run-parts /etc/cron.hourly
    17 0 * * * root run-parts /etc/cron.daily
    4 0 * * 0 root run-parts /etc/cron.weekly
    15 5 10 * * root run-parts /etc/cron.monthly

    This is a sample file content provided solely for illustration purposes. It shall not be copied to any server.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

0 Shares
Tweet
Share
Share
Buffer
Reddit
+1