Disable prefixing of user names in the ISPConfig3 control panel

botond published 2019/01/06, v - 11:01 time

Content

 

Introductory

When operating websites, it is very important to save data, make and keep copies of websites. And if we also develop the pages ourselves, it is essential to create a development environment. The best way to do this is to copy the pages on the server exactly to your home or work computer, and then copy the changes back when you have finished working on the website. All this, of course, automatically so that no error slips into the data movement.

In this brief tutorial we will make a small but useful setup for ISPConfig3 web hosting control panel. During setup, the prefixing of database names and database usernames is removed so that you do not have to manually change the database connection settings after the automated upload / sync of subsequent web pages due to the different client / web structure on the local machine.

The whole point is that ISPConfig prefixes the names of the database and other created users. This is done with the record data for that client. So if this client structure doesn't match on the local machine, you would have to manually rewrite the database connection settings in the pages' source code after synchronizing the web pages.

To avoid this, we make this very simple setup.

 

 

Configure ISPConfig3

Of course, this only works in an existing ISPConfig server environment, such as perfect server configuration Debian on 8 (Jessie) vagy Debian 9 (Stretch) -re.

Log in to ISPConfig as an Admin and navigate to System main menu - Interface section - Main config menu:

ISPConfig - System - Main config - prefix settings

Here we can also see the "factory" prefix settings of the database, FTP, Shell and WebDav users. Of these, the first two are the most important, i.e. the database name prefix and the database username prefix. Let's remove them. Of course, the others can be removed according to personal taste, I removed them all to make life easier when working on the server.

We will review the automated saving of web pages in another description.

 

Conclusion

This small setting is almost insignificant, but it can save us a lot of afterwork. Unfortunately, I only set it up later, so I had macera for a couple of syncs. It is advisable to do this at the beginning, of course only if you want to automatically synchronize the pages between the server and your home / work machine.