This is a server-administrator task. Back up /usr/local/directadmin/custombuild/options.conf and relevant custom templates. Identify the installed DirectAdmin version and the application requirements affected by the change.

1. Run da build opt_help or da build opt_help full to inspect available settings and descriptions for the installed version. Use the administrator CustomBuild options screen when preferred.
2. Compare the current value with the proposed value and confirm the option still exists. Do not reuse obsolete setting names from an old tutorial without checking current help.
3. Change only the required option through the supported interface or da build set command. Record the old and new values.
4. Read the option documentation to determine which build or configuration rewrite applies it. Saving an option alone does not necessarily rebuild the corresponding service.
5. Apply the narrow required operation during a maintenance window and keep its output. Avoid changing multiple unrelated stack choices in one experiment.

Confirm the saved option, actual installed component and generated configuration agree. Test the affected service and a representative application. Keep the working configuration under an administrative change record so future updates can be assessed against it.

If a value is rejected, use the current supported values rather than editing around validation. If the service fails after application, restore the previous option and the appropriate generated configuration or component through the supported workflow. A backup of options.conf alone is not a full rollback of binaries or data changed by an upgrade.

• Updating DirectAdmin software through CustomBuild safely
• Choosing Apache, nginx or nginx with Apache in DirectAdmin
• Providing multiple supported PHP versions in DirectAdmin
• Adding a PHP extension through DirectAdmin CustomBuild

• DirectAdmin: Custombuild Overview
• DirectAdmin: Customize Everything