bench new-site prompts for MySQL superuser manually even with automatic configurations

[absanr]

Issue: bench new-site prompts for MySQL superuser credentials manually

Description

When I run bench new-site on the container configured by Codespaces, the process stops by manually asking for MySQL superuser credentials with the message:

---

Actual Behavior

The command halts and does not proceed beyond the prompt for MySQL superuser credentials, effectively leaving the process stuck.

This issue occurred today, even though in November the same setup executed successfully without any interruptions.

---

Console Message

Files

---

Environment Details

• Operating System: Debian GNU/Linux 12 (bookworm)
• Frappe Version: 15.x.x-develop

[absanr]

Solution bench new-site

The issue of bench new-site interactively requesting the MySQL root password was resolved by removing manual interaction through specific script adjustments.

Implemented Solution

1. Repository Cloning:
   The base repository was cloned to apply the necessary modifications. The changes are available at the following link:
   View changes on GitHub

2. Script Permissions:
   Ensures that the script is executable.

   SCRIPT_PATH="$(realpath "$0")"
   chmod +x "$SCRIPT_PATH"
   echo "Permissions set for: $SCRIPT_PATH"

3. Automated bench new-site Execution:
   Configures the root user and other necessary parameters to create the site without manual intervention.

   create_site_with_root() {
     echo "Trying to create site with root user..."
     if ! bench new-site dev.localhost        
     --mariadb-root-username root        
     --mariadb-root-password 123        
     --admin-password admin        
     --db-host mariadb        
     --mariadb-user-host-login-scope=%; then
       echo "Critical error: Failed to create site using root."
       exit 1
     else
       echo "Site created successfully."
     fi
   }
   
   create_site_with_root

Results

• The setup process now runs seamlessly without requiring manual input for MySQL credentials.
• All changes are tracked and documented in the GitHub repository linked above.