Updating software manually

From time to time, you'll want to ensure your services are updated, not only for the new features, but to solve potential security issues as well.

With CustomBuild, this is simple, type:

cd /usr/local/directadmin/custombuild
./build update
./build versions
1
2
3

The last command will show currently used software version and if update is available. The actual command to update only available software:

./build update_versions
1

Optionally, there is a CustomBuild 2.0 pluginopen in new window which is installed by default with new installs, so you can control things through the DirectAdmin Admin Level interface.

Another commonly used command is to build all managed software. It is not recommended for regular use as it recompiles absolutely all software in use:

./build all
1

Updating software automatically

You can also set CustomBuild to regularly check for updates, and email you if there are any.

cd /usr/local/directadmin/custombuild
./build set cron yes
./build set cron_frequency weekly
./build set email your@email.com
./build set notifications  yes
./build set da_autoupdate yes
./build set clean_old_webapps yes
./build cron
1
2
3
4
5
6
7
8

Or even to autoupdate managed services by CustomBuild. Just keep in mind that the server admin is still required to be fully aware of the system and its state if he sets the system to be auto-updated:

./build set updates yes
./build cron
1
2

Update OS packages and managed by DA

CustomBuild version 2369 includes** update_versions_full**, update_full and update_versions full calls, they all do the same:

  1. Update OS packages

  2. Update CustomBuild and CustomBuild packages

Everything with just a single call like:

./build update_full
1

Override single package version

If you need to keep an older version of one item managed by CustomBuild (for whatever reason), a file called custom_versions.txt can do just that. It has the ability to override versions.txt entries with any item that is in the custom_versions.txt. That way, the versions.txt can be updated and custom_versions.txt will hold the override.

In this example, we'll use: (taken from versions.txt)

Let's say the active version of curl is 7.66.0, but we want to downgrade to To do it, run the following:

cd /usr/local/directadmin/custombuild
echo "curl:7.38.0:" >> custom_versions.txt
./build "curl"
1
2
3

Note that the ./build curl command might differ from versions.txt entry, so adjust it as needed, but that's the general idea.

Last Updated: 6/23/2021, 9:36:08 PM