Migrations, Cloning, and the WordPress Configuration File (wp-config.php)
Introduction
- A quick intro to user-configs.php
- Editing user-configs.php
- Migrating to GridPane and the wp-config.php file
If you have a website that requires you to add custom code snippets to the
wp-config.php
file, on GridPane these changes won’t persist when you migrate your website to a new server or clone it to a new domain name. Due to the way cloning works, a new
wp-config.php
will instead be generated in its place.
To remedy this, we have the
user-configs.php
which you can use to add your custom edits.
Also, if you migrate to GridPane and the migration process copies the wp-config.php file into your websites /htdocs folder, this may cause issues, and you will need to delete the none-GridPane wp-config.php file to ensure your site works as expected.
We’ll take a look at both of these below.
A Quick Intro to user-configs.php
user-configs.php
is a custom GridPane solution for adding content to wp-config.php without actually adding it directly to the
wp-config.php
file.
Code placed in this file is treated in the same way by WordPress as if it was added to the
wp-config.php
file. This is accomplished using the PHP include statement.
With this, you can make sure that your changes do persist over migrations/clones, by instead adding your code to the
user-configs.php
file. Any code added here will not be written over at any point by any GridPane function.
NOTE: This wouldn’t transfer over if moving a WordPress site away from GridPane, but it will make it so moving and cloning sites within GP is smooth sailing.
Editing users-config.php
The
user-configs.php
file is located in:
/var/www/site.url/user-configs.php
You can edit it either directly on your server, or over SFTP.
Edit via SFTP
To connect to your server over SFTP, please check out the following articles: –
Connecting to a GridPane Server by SFTP as the Root User
Connecting to a GridPane Server by SFTP as a System User
Once connected you can download the file over SFTP, make your edits, and then re-upload it to your server.
Edit via SSH
To connect to your server via SSH, see the following articles to get started:
Generate your SSH Key:
Generate SSH Key on Windows with Putty
Generate SSH Key on Windows with Windows Subsystem for Linux
Generate SSH Key on Windows with Windows CMD/PowerShell
Add your SSH Key to GridPane:
Add/Remove an SSH Key to/from an Active GridPane Server
Connect to your server:
Inside your server type the following command to edit your
user-configs.php
, replacing “site.url” with your domain name:
nano /var/www/site.url/user-configs.php
Make your edits, and then save the file with CTRL+O. You can then exit the file with CTRL+X, and then exit your server with:
exit
Once your edits are made you’re all set! If you migrate your website to a new server, or clone it to a new domain name, your custom edits will now persist.
Migrating to GridPane and the wp-config.php file
To ensure your migrations are successful, please double check that you don’t have two wp-config.php files inside your site as you move your sites to GridPane
GridPane securely stores the wp-config.php file 1 level up outside of /htdocs here:
/var/www/site.url
Depending on how you’ve migrated over, you find that you also have additional file here:
/var/www/site.url/htdocs
If you have two wp-config.php files these can interfere with each other and cause problems. Please simply delete the wp-config.php file inside /htdocs if it exists, and leave ours in it’s place.
You can do this by connecting to your server over SFTP or you can delete them directly on your server – please see the guides linked in the previous section to get started.
If deleting over SSH, you can navigate to your websites htdocs folder with the following command (switching out “site.url” for your websites domain name):
cd /var/www/site.url/htdocs
Then display the contents of the file with:
ls -l
And if you see a wp-config.php file, you can delete it with:
rm wp-config.php
Once that’s done you’re all set!