You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an actual security-related reason for choosing a random string as the database name for new WordPress sites? If not, CP should name databases and the database admin user the same as the website name, which is what CP already does when you use the "Create Database" sidebar option.
For example: ergo_wp1 user and db for the newly created WordPress under website ergodark.com.
This makes using something like mariadb CLI or phpMyAdmin less of an absolute chore.
The text was updated successfully, but these errors were encountered:
Xunnamius
changed the title
WordPress databases and database users should be named the same as the
WordPress databases and database users should be named based on the website name
Sep 1, 2023
Is there an actual security-related reason for choosing a random string as the database name for new WordPress sites? If not, CP should name databases and the database admin user the same as the website name, which is what CP already does when you use the "Create Database" sidebar option.
For example:
ergo_wp1
user and db for the newly created WordPress under websiteergodark.com
.This makes using something like
mariadb
CLI or phpMyAdmin less of an absolute chore.The text was updated successfully, but these errors were encountered: