Hi, when running the wordpress/new-site.sh I get the following output:

✔ success Function 'env_update_variable'
✘ ERROR   You must inform the required argument(s) to the function: 'env_update_variable' 
   Replace string: DOCKER_WORDPRESS_MYSQL_DATABASE

⚡ Start execution '/home/ubuntu/server/server-automation/wordpress/new-site.sh --yes':
 ✔ success Function 'check_local_env_file'
 ✔ success Function 'check_docker'
 ✔ success Function 'check_running_script'
 ✔ success Function 'starts_initial_check'
 ✔ success Function 'check_server_automation_env_file_exists'
 ✔ success Function 'check_folder_exists'
 ? question Please enter the URL for the Site:mytestsite.be
 ✔ success Function 'common_read_user_input'
 ✔ success Function 'domain_get_domain_from_url'
 ✔ success Function 'common_generate_random_string'
 ✔ success Function 'check_folder_exists'
 ✔ success Function 'common_create_folder'
 ✔ success Function 'git_clone_repo'
 ✔ success Function 'domain_get_main_name_from_url'
 ✔ success Function 'common_generate_random_string'
 ✔ success Function 'docker_check_container_is_running'
 ✔ success Function 'docker_check_container_is_running'
 ✔ success Function 'env_update_variable'
 ✔ success Function 'env_update_variable'
 ✔ success Function 'env_update_variable'
 ✔ success Function 'env_update_variable'
 ✔ success Function 'env_update_variable'
 ✔ success Function 'env_update_variable'
 ✔ success Function 'env_update_variable'
 ✔ success Function 'env_update_variable'
 ✘ ERROR   You must inform the required argument(s) to the function: 'env_update_variable' 
   Replace string: DOCKER_WORDPRESS_MYSQL_DATABASE

Any ideas on how to resolve this error?

Could it be possible to expose the db port ( port 3306 for mysql) to permit remote db management based for example on a (y/N) and a 'port number?' user input when running new-site.sh ?

Hi, I would like to use the server-automation to automatize the database backup of all my containers (wordpress and other apps).

I have cloned the repository and then within the cloned directory I changed the .env file setting the home path.
When I execute this command: ./backup.sh I get:

 Start execution '/home/john/docker/server-automation/backup/backup.sh ':
 ✔ success Function 'check_docker'
 ✔ success Function 'check_running_script'
 ✔ success Function 'starts_initial_check'
 ✔ success Function 'check_server_automation_env_file_exists'
 ✘ ERROR   Folder '/home/john/server-automation/sites' does not exist

I also noticed that the youtube video is outdate and the wiki link point to a 404.
Could you please help me to configure this?

Hi there and thanks for the amazing work you've done.

When using this in my .env:

#Site image
SITE_IMAGE=wordpress
SITE_VERSION=6.2

The WP cli doesn't work.

I'm don't know how to troubleshoot further. I ran into the problem when trying to use the update site name script provided in the wordpress folder.

I may have tracked it down to the Wordpress version. It works when I use 4.6 for the site version.

Any pointers on how to troubleshoot would be awesome!

Thanks again.

edit:
The output i get when trying to run wp.sh is: (I replaced my domain with "site" in the following)

...:/home/root/server/sites/dev2.site.org/compose# ./wp.sh
/snap/docker/2746/lib/python3.6/site-packages/paramiko/transport.py:32: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography. The next release of cryptography (40.0) will be the last to support Python 3.6.
from cryptography.hazmat.backends import default_backend
Creating site-m0dff_wpcli_run ... done
Error: Error establishing a database connection.
ERROR: 1

Found issues where the project name is not valid with new docker compose requirements.

See: docker/compose#9519

This is how I fixed it. I don't know what problems would be caused by changing the common function in the base script. I am only using this set up for Wordpress, so I don't see a problem in my environment.

tawmeh@a1fbc70
tawmeh/basescript@9e7c669

just a suggestion:
it will may be more 'user friendly' to change line 601 in new-site.sh
LOCAL_MYSQL_USER=${LOCAL_SITE_NAME:1:10}"_user"
with
LOCAL_MYSQL_USER=${LOCAL_SITE_NAME:0::10}"_user"